Given the nature of the vulnerability the only salient mitigation strategy is to restrict interaction with the application to trusted files.
However, FileOpen does not mandate support for all supported.
These vendors have incorporated modules from FileOpen that enable the same controls as the ones implemented in the Adobe products. POST 0-day UPDATE: 08/26/17 - The vendor sent patch links to ZDI PDF Documents encrypted using the FileOpen software can be opened in a number of viewers other than Adobe Acrobat/Reader. "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."Ġ5/18/17 - ZDI disclosed report to vendorĠ6/26/17 - Vendor indicated that they could not reproduce the issueĠ6/26/17 - Vendor requested further repro detailsĠ7/06/17 - ZDI replied with sample scenario and the re-iterated the need for a fixĠ7/20/17 - The vendor indicated this will not be fixed because this can be mitigated by Secure ModeĠ8/08/17 - ZDI communicated that the proposed mitigation is not a fix and that the case will move to 0-day status This vulnerability is being disclosed publicly without a patch in accordance with the ZDI 120 day deadline. An attacker can leverage this vulnerability to execute code under the context of the current process. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. The specific flaw exists within app.launchURL method. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Foxit Reader. August 17th, 2017 (0Day) Foxit Reader launchURL Command Injection Remote Code Execution Vulnerability ZDI-17-691
0 kommentar(er)
