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

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

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

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

Iphone Os CVE-2015-7499

MEDIUM

Buffer Overflow (CWE-119)

2015-12-15 secalert@redhat.com

Buffer Overflow Iphone Os Mac Os X Tvos Watchos Ubuntu Linux Enterprise Linux Desktop Enterprise Linux Hpc Node Enterprise Linux Server Enterprise Linux Workstation Icewall Federation Agent Icewall File Manager Libxml2 Debian Linux Leap Opensuse

5.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

5.0 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Dec 15, 2015 - 21:59 cve.org

MEDIUM 5.0

DescriptionCVE.org

Heap-based buffer overflow in the xmlGROW function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive process memory information via unspecified vectors.

AnalysisAI

Heap-based buffer overflow in the xmlGROW function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive process memory information via unspecified vectors. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity.

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. Heap-based buffer overflow in the xmlGROW function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive process memory information via unspecified vectors. Affected products include: Apple Iphone Os, Apple Mac Os X, Apple Tvos, Apple Watchos, Canonical Ubuntu Linux. Version information: before 2.9.3.

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.