LiveActive security incident?Get immediate response
CVE Record

CVE-2013-0340: expat before version 2.4.0 does not properly handle entities expansion unless an application developer uses...

expat before version 2.4.0 does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler 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 expat 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

CVE-2013-0340 concerns how older libexpat handles XML entity expansion. Applications that parse attacker-supplied XML may be exposed to denial of service, internal HTTP requests, or file reads, depending on parser configuration and application behavior. The record notes debate over whether this is an expat issue or application responsibility. Exposure is most likely indirect: products, services, or OS packages embedding older libexpat and parsing untrusted XML. Risk depends heavily on application parser configuration, XML input sources, and whether external entities are disabled. Treat as a targeted exposure review rather than an emergency by default. Prioritize internet-facing or partner-facing systems that accept XML, especially legacy platforms, because impact can include service disruption and internal data access. Mitigation focus: Inventory applications and packages that embed or link libexpat.; Upgrade libexpat where vendor guidance identifies vulnerable versions.; Disable external entity expansion for XML parsing where supported..

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-0340 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
11Source links

CVSS and timeline data

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorlibexpatlibexpat, 0unaffected
Weakness

CWE details

No CWE listed

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