CVE-2013-0339
Last modified
CVE-2013-0339 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 4.42% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| 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 | — |
| Xmlsoft | Libxml2 | 1.8.2 | — |
| Xmlsoft | Libxml2 | 1.8.3 | — |
| Xmlsoft | Libxml2 | 1.8.4 | — |
| Xmlsoft | Libxml2 | 1.8.5 | — |
| Xmlsoft | Libxml2 | 1.8.6 | — |
| Xmlsoft | Libxml2 | 1.8.7 | — |
| Xmlsoft | Libxml2 | 1.8.9 | — |
| Xmlsoft | Libxml2 | 1.8.10 | — |
| Xmlsoft | Libxml2 | 1.8.13 | — |
| Xmlsoft | Libxml2 | 1.8.14 | — |
| Xmlsoft | Libxml2 | 1.8.16 | — |
| Xmlsoft | Libxml2 | 2.0.0 | — |
| Xmlsoft | Libxml2 | 2.1.0 | — |
| Xmlsoft | Libxml2 | 2.1.1 | — |
| Xmlsoft | Libxml2 | 2.2.0 | — |
| Xmlsoft | Libxml2 | 2.2.1 | — |
| Xmlsoft | Libxml2 | 2.2.2 | — |
| Xmlsoft | Libxml2 | 2.2.3 | — |
| Xmlsoft | Libxml2 | 2.2.4 | — |
| Xmlsoft | Libxml2 | 2.2.5 | — |
| Xmlsoft | Libxml2 | 2.2.6 | — |
| Xmlsoft | Libxml2 | 2.2.7 | — |
| Xmlsoft | Libxml2 | 2.2.8 | — |
| Xmlsoft | Libxml2 | 2.2.9 | — |
| Xmlsoft | Libxml2 | 2.2.10 | — |
| Xmlsoft | Libxml2 | 2.2.11 | — |
| Xmlsoft | Libxml2 | 2.3.0 | — |
| Xmlsoft | Libxml2 | 2.3.1 | — |
| Xmlsoft | Libxml2 | 2.3.2 | — |
| Xmlsoft | Libxml2 | 2.3.3 | — |
| Xmlsoft | Libxml2 | 2.3.4 | — |
| Xmlsoft | Libxml2 | 2.3.5 | — |
| Xmlsoft | Libxml2 | 2.3.6 | — |
| Xmlsoft | Libxml2 | 2.3.7 | — |
| Xmlsoft | Libxml2 | 2.3.8 | — |
| Xmlsoft | Libxml2 | 2.3.9 | — |
| Xmlsoft | Libxml2 | 2.3.10 | — |
| Xmlsoft | Libxml2 | 2.3.11 | — |
| Xmlsoft | Libxml2 | 2.3.12 | — |
| Xmlsoft | Libxml2 | 2.3.13 | — |
| Xmlsoft | Libxml2 | 2.3.14 | — |
| Xmlsoft | Libxml2 | 2.4.1 | — |
Showing 50 of 133 affected configurations. See NVD for the full list.
References
- http://secunia.com/advisories/52662Vendor Advisory
- http://secunia.com/advisories/55568Vendor Advisory
- http://secunia.com/advisories/52662Vendor Advisory
- http://secunia.com/advisories/55568Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-0339?
How severe is CVE-2013-0339?
How do I fix CVE-2013-0339?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2013
- CVE-2013-0333lib/active_support/json/backends/yaml.rb in Ruby on Rails 2.…
- CVE-2013-0334Bundler before 1.7, when multiple top-level source lines are…
- CVE-2013-0335OpenStack Compute (Nova) Grizzly, Folsom (2012.2), and Essex…7.6
- CVE-2013-0336The ipapwd_chpwop function in daemons/ipa-slapi-plugins/ipa-…
- CVE-2013-0337The default configuration of nginx, possibly 1.3.13 and earl…
- CVE-2013-0338libxml2 2.9.0 and earlier allows context-dependent attackers…
- CVE-2013-0340expat before version 2.4.0 does not properly handle entities…
- CVE-2013-0341Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2013-0342The CreateID function in packet.py in pyrad before 2.1 uses …4.3
- CVE-2013-0343The ipv6_create_tempaddr function in net/ipv6/addrconf.c in …
- CVE-2013-0344Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2013-0345varnish 3.0.3 uses world-readable permissions for the /var/l…
Are you affected by CVE-2013-0339?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
