CVE-2013-0339
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 3.6% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.6% in the next 30 days (EPSS).
- Severity: 6.8 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.6% · EPSS, next 30 days
- Weakness
- CWE-264
- Record status
- Modified
Affected
- Xmlsoft libxml2 ≤ 2.9.1
- Xmlsoft libxml2 1.7.0
- Xmlsoft libxml2 1.7.1
- Xmlsoft libxml2 1.7.2
- Xmlsoft libxml2 1.7.3
- Xmlsoft libxml2 1.7.4
- Xmlsoft libxml2 1.8.0
- Xmlsoft libxml2 1.8.1
Attack profile CVSS 2.0 · 6.8
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2013-0339.md and follow it. Check whether this project is affected by CVE-2013-0339. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://secunia.com/advisories/52662
- http://secunia.com/advisories/55568
- https://git.gnome.org/browse/libxml2/commit/?id=4629ee02ac649c27f9c0cf98ba017c6b5526070f
- http://secunia.com/advisories/52662
- http://secunia.com/advisories/55568
- https://git.gnome.org/browse/libxml2/commit/?id=4629ee02ac649c27f9c0cf98ba017c6b5526070f
References
- http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00002.html
- http://openwall.com/lists/oss-security/2013/02/21/24
- http://openwall.com/lists/oss-security/2013/02/22/3
- http://seclists.org/oss-sec/2013/q4/182
- http://seclists.org/oss-sec/2013/q4/184
- http://seclists.org/oss-sec/2013/q4/188
- http://secunia.com/advisories/52662
- http://secunia.com/advisories/54172
- http://secunia.com/advisories/55568
- http://www.debian.org/security/2013/dsa-2652
- http://www.openwall.com/lists/oss-security/2013/04/12/6
- http://www.ubuntu.com/usn/USN-1904-1
- http://www.ubuntu.com/usn/USN-1904-2
- https://bugzilla.redhat.com/show_bug.cgi?id=915149
- https://git.gnome.org/browse/libxml2/commit/?id=4629ee02ac649c27f9c0cf98ba017c6b5526070f
- http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00002.html
- http://openwall.com/lists/oss-security/2013/02/21/24
- http://openwall.com/lists/oss-security/2013/02/22/3
- http://seclists.org/oss-sec/2013/q4/182
- http://seclists.org/oss-sec/2013/q4/184
- http://seclists.org/oss-sec/2013/q4/188
- http://secunia.com/advisories/52662
- http://secunia.com/advisories/54172
- http://secunia.com/advisories/55568
- http://www.debian.org/security/2013/dsa-2652