Login Request a demo
High severity · published Apr 24, 2018
CVE-2017-17557
In Foxit Reader before 9.1 and Foxit PhantomPDF before 9.1, a flaw exists within the parsing of the BITMAPINFOHEADER record in BMP files
8.8
CVSS
3.5%
EPSS
No
On KEV
Description
In Foxit Reader before 9.1 and Foxit PhantomPDF before 9.1, a flaw exists within the parsing of the BITMAPINFOHEADER record in BMP files. The issue results from the lack of proper validation of the biSize member, which can result in a heap based buffer overflow. An attacker can leverage this to execute code in the context of the current process.
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)3.5% · higher than 89% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
FR
Foxit Reader · Foxitsoftware
before 9.1 · source: NVD
PH
Phantompdf · Foxitsoftware
before 9.1 · source: NVD
Affected product
FR
Foxit Reader
Foxitsoftware
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2017-17557
CVE.org
https://www.cve.org/CVERecord?id=CVE-2017-17557
Third Party Advisory
http://www.securityfocus.com/bid/103999
Third Party Advisory
http://www.securitytracker.com/id/1040733
Third Party Advisory
https://blog.0patch.com/2018/05/0patching-foxit-reader-buffer-oops.html
Vendor Advisory
https://www.foxitsoftware.com/support/security-bulletins.php
More from Foxit Reader
9.8
CVE-2021-38574
An issue was discovered in Foxit Reader and PhantomPDF before 10.1.4
9.8
CVE-2021-38573
An issue was discovered in Foxit Reader and PhantomPDF before 10.1.4
9.8
CVE-2021-38572
An issue was discovered in Foxit Reader and PhantomPDF before 10.1.4
9.8
CVE-2021-38568
An issue was discovered in Foxit Reader and PhantomPDF before 10.1.4
9.8
CVE-2021-33793
Foxit Reader before 10.1.4 and PhantomPDF before 10.1.4 have an out-of-bounds write because the Cross-Reference table is mishandled during Office document conversion