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

CVE-2015-3633 has a CVSS 2.0 base score of 5.0 (Medium). CVSS vector: AV:N/AC:L/Au:N/C:N/I:N/A:P. EPSS exploitation probability: 0.1%.

Is there a patch available for CVE-2015-3633?

Yes, a patch is available for CVE-2015-3633. Update the affected software to the latest version immediately.

Enterprise Reader CVE-2015-3633

MEDIUM

Buffer Overflow (CWE-119)

2015-05-01 cve@mitre.org

Denial Of Service Buffer Overflow Enterprise Reader Foxit Reader Phantompdf

5.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

5.0 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

May 01, 2015 - 15:59 cve.org

MEDIUM 5.0

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 vectors related to digital signatures.

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 vectors related to digital signatures. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity. This Buffer Overflow vulnerability could allow attackers to corrupt memory to execute arbitrary code or crash the application.

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 vectors related to digital signatures. Affected products include: Foxitsoftware Enterprise Reader, Foxitsoftware Foxit Reader, Foxitsoftware Phantompdf. Version information: before 7.1.5.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.