CVE-2017-10952
Summary
| CVE | CVE-2017-10952 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2017-08-29 13:29:00 UTC |
| Updated | 2019-10-09 23:21:00 UTC |
| Description | This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Foxit Reader 8.2.0.2051. 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. Was ZDI-CAN-4518. |
Risk And Classification
Problem Types: CWE-20
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Foxitsoftware | Foxit Reader | 8.2.0.2051 | All | All | All |
| Application | Foxitsoftware | Foxit Reader | 8.2.0.2051 | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Zero Day Initiative | MISC | zerodayinitiative.com | Third Party Advisory, VDB Entry |
| Foxit Reader CVE-2017-10952 Remote Code Execution Vulnerability | BID | www.securityfocus.com | Third Party Advisory, VDB Entry |
| Foxit Reader File Input Validation Flaw in 'saveAs' JavaScript Function Lets Remote Users Write Files and Execute Arbitrary Code - SecurityTracker | SECTRACK | www.securitytracker.com | Third Party Advisory, VDB Entry |
| 0patch Blog: 0patching Foxit Reader's saveAs "0day" (CVE-2017-10952) | MISC | 0patch.blogspot.com | Exploit, Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.