TippingPoint Zero Day Initiative
 

(0Day) Foxit Reader saveAs Arbitrary File Write Remote Code Execution Vulnerability

ZDI-17-692: August 17th, 2017

CVE ID

CVSS Score

Affected Vendors

Affected Products

TippingPoint™ IPS Customer Protection

TippingPoint IPS customers are protected against this vulnerability by Digital Vaccine protection filter ID 28921. For further product information on the TippingPoint IPS:

Vulnerability Details


This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Foxit Reader. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the saveAs JavaScript function. The issue results from the lack of proper validation of user-supplied data, which can lead to writing arbitrary files into attacker controlled locations. An attacker can leverage this vulnerability to execute code under the context of the current process.

Vendor Response

Foxit states:


This vulnerability is being disclosed publicly without a patch in accordance with the ZDI 120 day deadline.

"Foxit Reader & PhantomPDF has a Safe Reading Mode which is enabled by default to control the running of JavaScript, which can effectively guard against potential vulnerabilities from unauthorized JavaScript actions."

06/22/17 - ZDI disclosed report to vendor
06/22/17 - Vendor acknowledged and communicated fix would be included in next version
06/22/17 - The vendor indicated this will not be fixed because this can be mitigated by Secure Mode
07/06/17 - ZDI replied with sample scenario and the re-iterated the need for a fix
07/20/17 - The vendor indicated this will not be fixed because this can be mitigated by Secure Mode
08/08/17 - ZDI communicated that the proposed mitigation is not a fix and that the case will move to 0-day status
POST 0-day UPDATE: 08/26/17 - The vendor sent patch links to ZDI https://www.foxitsoftware.com/products/pdf-reader/

-- Mitigation:
Given the nature of the vulnerability the only salient mitigation strategy is to restrict interaction with the application to trusted files.


Disclosure Timeline

    2017-06-22 - Vulnerability reported to vendor
    2017-08-17 - Coordinated public release of advisory

Credit

This vulnerability was discovered by:
    Steven Seeley (mr_me) of Offensive Security