LiveActive security incident?Get immediate response
CVE Record

CVE-2013-0339: libxml2 through 2.9.1 does not properly handle external entities expansion unless an application developer...

libxml2 through 2.9.1 does not properly handle external entities expansion unless an application developer uses the xmlSAX2ResolveEntity or xmlSetExternalEntityLoader function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because libxml2 already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed and each affected application would need its own CVE.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an XML External Entity issue in libxml2 through 2.9.1. If an application parses attacker-supplied XML without safely handling external entities, it may expose files, trigger internal HTTP requests, or consume resources. The business risk depends on which applications use libxml2 and whether they accept untrusted XML. Exposure is most likely in legacy systems, services, or tools that use libxml2 through 2.9.1 to parse XML from users, partners, uploads, APIs, or message queues. Systems that never parse untrusted XML or that disable external entity expansion are less exposed. Treat as a targeted remediation item, not an emergency solely from the provided evidence. Prioritize internet-facing or partner-facing XML workflows, legacy systems, and software that bundles old libxml2 versions. Ask teams to prove parser hardening, not only package version status. Mitigation focus: Inventory applications and packages using libxml2 through 2.9.1.; Apply relevant vendor libxml2 updates from supported distributions.; Disable external entity expansion for untrusted XML parsing..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-0339 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.