Home/CVE/The xmlParseMisc function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of se
CVE
↯ PDF report

CVE-2015-75002

The xmlParseMisc function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of se

The xmlParseMisc function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service (out-of-bounds heap read) via unspecified vectors related to incorrect entities boundaries and start tags.

MEDIUM · CVSS 5 EPSS 0.05917
EPSS exploitation odds5.92% · top 7%
Schedule remediation
  • EPSS percentile: top 8% of all CVEs by exploitation likelihood
  • Public exploit or PoC is available
No Sigma yet — build one → YARA rules0
Look this up elsewhere - one-click external pivots
NVDCVE.orgCISAExploit-DBGitHub PoCVulnCheck KEVGreyNoise
▸ How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2015-7500, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
⚠

Exploitation evidence

1 of 7 sources
Corroboration score 8/100 · emerging. This counts how many independent sources have exploitation evidence, and separates two different things: confirmed in-the-wild use (CISA KEV, Microsoft MSRC, ransomware activity) from exploit / PoC availability (Metasploit, ExploitDB, Nuclei, public PoCs). A template or PoC existing means an attack is possible and easy - it is not, on its own, proof the CVE is being exploited in the wild.
Exploit / PoC available
public PoC
↗

Exploitation momentum

1237 days of EPSS
stable
Exploitation pressure is steady. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
Window
▣

Severity & exploitation scoring

CVSS base score
5
MEDIUMCVSS v3.1 · [email protected]
EPSS exploitation probability
5.92%
Top 7%odds of exploitation in the next 30 days
CVSS metric silhouette
No structured CVSS vector for this CVE. Older entries often have only a numeric base score - the metric breakdown radar requires a full AV:_/AC:_/... vector string published by NVD.
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
Lifecycle
  1. 15 Dec 2015Published to NVD
  2. 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
→
⚠

Public Exploits & PoCs

2
These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
poc Live-Hack-CVE/CVE-2015-7500 (trickest)↗ date unknown
⋮
Vote & rate
Report or claim
⚠ Report this PoC

Becomes a public comment attributed as First L. (never full last name). Don't include private info. Rate-limited: 5/hour.

Works? no reports yet
Rating -
poc akaganeite/CVE4PP (trickest)↗ date unknown
⋮
Vote & rate
Report or claim
⚠ Report this PoC

Becomes a public comment attributed as First L. (never full last name). Don't include private info. Rate-limited: 5/hour.

Works? no reports yet
Rating -
◆

ATT&CK techniques

1

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1499 · Endpoint Denial of Service
▤ Build a SIEM detection for these techniques
▤

CAPEC attack patterns

12

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-10 · Buffer Overflow via Environment Variables CAPEC-CAPEC-100 · Overflow Buffers CAPEC-CAPEC-123 · Buffer Manipulation CAPEC-CAPEC-14 · Client-side Injection-induced Buffer Overflow CAPEC-CAPEC-24 · Filter Failure through Buffer Overflow CAPEC-CAPEC-42 · MIME Conversion CAPEC-CAPEC-44 · Overflow Binary Resource File CAPEC-CAPEC-45 · Buffer Overflow via Symbolic Links CAPEC-CAPEC-46 · Overflow Variables and Tags CAPEC-CAPEC-47 · Buffer Overflow via Parameter Expansion CAPEC-CAPEC-8 · Buffer Overflow in an API Call CAPEC-CAPEC-9 · Buffer Overflow in Local Command-Line Utilities
⬡

Weakness Classification

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
▤

Affected Products & Versions

13
hp icewall federation agentall versions
hp icewall file managerall versions
xmlsoft libxml2<= 2.9.2
debian linuxall versions
apple iphone os<= 9.2.1
apple mac os x<= 10.11.3
apple tvos<= 9.1
apple watchos<= 2.1
redhat enterprise linux desktopall versions
redhat enterprise linux hpc nodeall versions
redhat enterprise linux serverall versions
redhat enterprise linux workstationall versions
canonical ubuntu linuxall versions
▤

Related CVEs

8
CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-1999-0027 root privileges via buffer overflow in eject command on SGI IRIX systems. 3 same CWE-119 CVE-1999-0069 Solaris ufsrestore buffer overflow. 2 same CWE-119 HIGH CVE-1999-0002 Buffer overflow in NFS mountd gives root access to remote attackers, mostly in L... 1 same CWE-119 CVE-1999-0332 Buffer overflow in NetMeeting allows denial of service and remote command execut... same CWE-119 CVE-2015-7942 The xmlParseConditionalSections function in parser.c in libxml2 does not properl... same product CVE-2015-5312 The xmlStringLenDecodeEntities function in parser.c in libxml2 before 2.9.3 does... same product CVE-2015-7497 Heap-based buffer overflow in the xmlDictComputeFastQKey function in dict.c in l... same product CVE-2015-7498 Heap-based buffer overflow in the xmlParseXmlDecl function in parser.c in libxml... same product
📦

Fixed versions by distribution

13
The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
oracle alllibxml2 open
oracle alllibxml2-devel open
oracle alllibxml2-python open
oracle alllibxml2-static open
suse sle15libxml2 open
suse sle15libxml2-2 fixed in 0:2.9.7-1.30
suse sle15libxml2-2-32bit fixed in 0:2.10.3-150500.5.14.1
suse sle15libxml2-devel fixed in 0:2.9.7-3.6.1
suse sle15libxml2-tools fixed in 0:2.10.3-150500.5.14.1
suse sle15python3-libxml2 fixed in 0:2.10.3-150500.5.14.1
suse sle15python3-libxml2-python fixed in 0:2.9.7-3.19.10
suse sle15python311-libxml2 fixed in 0:2.10.3-150500.5.14.1
suse sle15ruby2.5-rubygem-nokogiri fixed in 0:1.8.5-150400.14.3.1
⚑

Vendor Advisories

16
suse-csafopenSUSE-SU-2026:10356-1
suse-csafopenSUSE-SU-2025:14697-1
suse-csafopenSUSE-SU-2024:14174-1
suse-csafopenSUSE-SU-2024:10192-1
suse-csafopenSUSE-SU-2024:10549-1
suse-csafopenSUSE-SU-2024:11340-1
suse-csafopenSUSE-SU-2024:11912-1
suse-csafopenSUSE-SU-2024:13165-1
suse-csafSUSE-SU-2016:0786-1
rhsaRHSA-2016:1089Moderate
suse-csafSUSE-SU-2016:0049-1
suse-csafSUSE-SU-2016:0030-1
usnUSN-2834-1
suse-csafrhsa-2015_2550
rhsaRHSA-2015:2550Moderate
rhsaRHSA-2015:2549Moderate
🔗

References & Sources

25
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
http://lists.apple.com/archives/security-announce/2016/Mar/msg00000.html
Mailing ListThird Party Advisory
http://lists.apple.com/archives/security-announce/2016/Mar/msg00001.html
Mailing ListThird Party Advisory
http://lists.apple.com/archives/security-announce/2016/Mar/msg00002.html
Mailing ListThird Party Advisory
http://lists.apple.com/archives/security-announce/2016/Mar/msg00004.html
Mailing ListThird Party Advisory
http://lists.opensuse.org/opensuse-updates/2015-12/msg00120.html
http://lists.opensuse.org/opensuse-updates/2016-01/msg00031.html
http://marc.info/?l=bugtraq&m=145382616617563&w=2
Third Party Advisory
http://rhn.redhat.com/errata/RHSA-2015-2549.html
Third Party Advisory
http://rhn.redhat.com/errata/RHSA-2015-2550.html
Third Party Advisory
http://rhn.redhat.com/errata/RHSA-2016-1089.html
http://www.debian.org/security/2015/dsa-3430
Third Party Advisory
http://www.oracle.com/technetwork/topics/security/bulletinjan2016-2867206.html
http://www.oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.html
http://www.securityfocus.com/bid/79562
http://www.securitytracker.com/id/1034243
http://www.ubuntu.com/usn/USN-2834-1
Third Party Advisory
http://xmlsoft.org/news.html
Vendor Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=1281943
Issue Tracking
https://git.gnome.org/browse/libxml2/commit/?id=f1063fdbe7fa66332bbb76874101c2a7b51b519f
https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c04944172
Third Party Advisory
https://security.gentoo.org/glsa/201701-37
https://support.apple.com/HT206166
Vendor Advisory
https://support.apple.com/HT206167
Vendor Advisory
https://support.apple.com/HT206168
Vendor Advisory
https://support.apple.com/HT206169
Vendor Advisory
◈SOC and Response
◆Detection Engineering
◎Threat Hunting
▲Red Team and Pentest
■Compliance and GRC
◯About
threatengine.sh Crafted with love in Toronto, Canada