What is the CVSS score of CVE-2015-3632?

CVE-2015-3632 has a CVSS 2.0 base score of 4.3 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:N/I:N/A:P. EPSS exploitation probability: 6.8%.

Is there a public PoC exploit available for CVE-2015-3632?

Yes, a public proof-of-concept exploit is available for CVE-2015-3632. Prioritise patching immediately. EPSS: 6.8%.

Enterprise Reader CVE-2015-3632

MEDIUM

Buffer Overflow (CWE-119)

2015-05-01 cve@mitre.org

Denial Of Service Buffer Overflow Enterprise Reader Foxit Reader Phantompdf

4.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

AV:N/AC:M/Au:N/C:N/I:N/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:N/C:N/I:N/A:P

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

May 01, 2015 - 15:59 cve.org

MEDIUM 4.3

DescriptionCVE.org

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.

AnalysisAI

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. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. 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. Affected products include: Foxitsoftware Enterprise Reader, Foxitsoftware Foxit Reader, Foxitsoftware Phantompdf. Version information: before 7.1.5.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.