CVE-2015-3632 json
Foxit Reader, Enterprise Reader, and PhantomPDF before 7.1.5 allow remote attackers to cause a denial of service (memory corruption and cra…
published 2015-05-01 11 y ago modified 2026-06-17 4 mo ago also EUVD-2015-3670
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.0%
- EPSS 6.0% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
Foxit Reader, Enterprise Reader, and PhantomPDF before 7.1.5 allow remote attackers to cause a denial of service (memory corruption and crash) via a crafted GIF in a PDF file.
Timeline
- First public exploit (EDB-36859)
- Published
Exploit prediction
6.03% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-36859 Foxit Reader PDF 7.1.3.320 - Parsing Memory Corruption local, 2015-04-29
- packetstormsecurity.com http://packetstormsecurity.com/files/131685/Foxit-Reader-7.1.3.320-Memory-Corruption.html referenced PoC, tagged "exploit" by a source, unverified
- protekresearchlab.com http://protekresearchlab.com/PRL-2015-05/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/36859/
exploit, third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/131685/Foxit-Reader-7.1.3.320-Memory-Corruption.html
exploit, third-party-advisory, vdb-entry
-
protekresearchlab.com
/PRL-2015-05/
exploit
-
foxitsoftware.com
/support/security_bulletins.php#FRD-27
vendor-advisory
-
securitytracker.com
/id/1032229
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/74418
vdb-entry
Sources
- CVE List CVE-2015-3632
- NVD CVE-2015-3632
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.