{"id":"CVE-2013-0339","aliases":["BELL-CVE-2013-0339","DEBIAN-CVE-2013-0339","DSA-2652-1","EUVD-2013-0351","GHSA-4qgp-72gr-jfg9"],"status":"published","title":"libxml2 through 2.9.1 does not properly handle external entities expansion unless an application...","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.","severity":{"version":"2.0","score":6.8,"vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.03609,"percentile":0.89563,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-264"],"published":"2013-03-24T00:00:00Z","modified":"2026-09-01T20:03:11Z","fixes":[{"ecosystem":"Debian:12","package":"libxml2","fixed_in":["2.8.0+dfsg1-7+nmu1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"libxml2","fixed_in":["2.8.0+dfsg1-7+nmu1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"libxml2","fixed_in":["2.8.0+dfsg1-7+nmu1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"libxml2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.0+dfsg1-7+nmu1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"libxml2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.0+dfsg1-7+nmu1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"libxml2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.0+dfsg1-7+nmu1"}]}]},{"source":"osv","ecosystem":"Debian:6.0","package":"libxml2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.8.dfsg-2+squeeze7"}]}],"versions":["2.7.8.dfsg-2","2.7.8.dfsg-2+squeeze1","2.7.8.dfsg-2+squeeze2","2.7.8.dfsg-2+squeeze3","2.7.8.dfsg-2+squeeze4","2.7.8.dfsg-2+squeeze5","2.7.8.dfsg-2+squeeze6"],"bundled":2}],"products":[{"vendor":"canonical","product":"ubuntu_linux"},{"vendor":"debian","product":"debian_linux"},{"vendor":"suse","product":"linux_enterprise_server"},{"vendor":"xmlsoft","product":"libxml2"}],"references":[{"url":"http://secunia.com/advisories/52662","tags":["third-party-advisory","x_refsource_SECUNIA","x_transferred","Vendor Advisory","advisory"]},{"url":"http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00002.html","tags":["vendor-advisory","x_refsource_SUSE","x_transferred","web"]},{"url":"http://openwall.com/lists/oss-security/2013/02/21/24","tags":["mailing-list","x_refsource_MLIST","x_transferred","web"]},{"url":"http://openwall.com/lists/oss-security/2013/02/22/3","tags":["mailing-list","x_refsource_MLIST","x_transferred","web"]},{"url":"http://seclists.org/oss-sec/2013/q4/188","tags":["mailing-list","x_refsource_MLIST","x_transferred","web"]},{"url":"http://seclists.org/oss-sec/2013/q4/184","tags":["mailing-list","x_refsource_MLIST","x_transferred","web"]},{"url":"http://seclists.org/oss-sec/2013/q4/182","tags":["mailing-list","x_refsource_MLIST","x_transferred","web"]},{"url":"http://www.ubuntu.com/usn/USN-1904-2","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","advisory"]},{"url":"http://www.ubuntu.com/usn/USN-1904-1","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","advisory"]},{"url":"http://www.debian.org/security/2013/dsa-2652","tags":["vendor-advisory","x_refsource_DEBIAN","x_transferred","advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=915149","tags":["x_refsource_MISC","x_transferred","report"]},{"url":"http://secunia.com/advisories/54172","tags":["third-party-advisory","x_refsource_SECUNIA","x_transferred","advisory"]},{"url":"http://secunia.com/advisories/55568","tags":["third-party-advisory","x_refsource_SECUNIA","x_transferred","Vendor Advisory","advisory"]},{"url":"https://git.gnome.org/browse/libxml2/commit/?id=4629ee02ac649c27f9c0cf98ba017c6b5526070f","tags":["x_refsource_MISC","x_transferred","Exploit","Patch","evidence","fix"]},{"url":"http://www.openwall.com/lists/oss-security/2013/04/12/6","tags":["mailing-list","x_refsource_MLIST","x_transferred","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2013-0339"},{"url":"https://github.com/advisories/GHSA-4qgp-72gr-jfg9"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2013-0339","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2013-0339","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2013-0339","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.","status":"published","published":"2014-01-21T18:00:00Z","modified":"2024-08-06T14:25:09.789Z","updated_at":"2026-11-02T14:34:59.222149Z"}],"euvd":[{"id":"EUVD-2013-0351","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.","status":"published","published":"2014-01-21T18:00:00Z","modified":"2024-08-06T14:25:09Z","updated_at":"2026-11-03T01:56:45.704567Z"}],"ghsa":[{"id":"GHSA-4qgp-72gr-jfg9","title":"libxml2 through 2.9.1 does not properly handle external entities expansion unless an application...","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.","status":"published","published":"2022-05-05T02:48:53Z","modified":"2023-02-01T05:02:02Z","updated_at":"2026-11-02T14:49:49.585103Z"}],"nvd":[{"id":"CVE-2013-0339","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.","status":"published","published":"2014-01-21T18:55:09.053Z","modified":"2026-06-16T23:49:15.62Z","cvss":[{"version":"2.0","score":6.8,"vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-264"],"updated_at":"2026-11-02T14:02:48.062712Z"}],"osv":[{"id":"BELL-CVE-2013-0339","title":"CVE-2013-0339 does not affect BellSoft software","status":"withdrawn","published":"2014-01-21T18:55:00Z","modified":"2026-01-28T07:19:55.575552Z","cvss":[{"version":"2.0","score":6.8,"vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","level":"medium"}],"updated_at":"2026-11-02T15:28:13.47097Z"},{"id":"CVE-2013-0339","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.","status":"published","published":"2014-01-21T18:55:09Z","modified":"2026-04-10T03:42:39.837099Z","updated_at":"2026-11-02T15:43:58.802805Z"},{"id":"DEBIAN-CVE-2013-0339","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.","status":"published","published":"2014-01-21T18:55:09.053Z","modified":"2026-09-01T20:03:11.373267078Z","updated_at":"2026-11-02T15:45:25.218101Z"},{"id":"DSA-2652-1","title":"libxml2 - external entity expansion","status":"published","published":"2013-03-24T00:00:00Z","modified":"2026-03-09T01:22:07.11377Z","updated_at":"2026-11-02T15:46:15.489951Z"}]}}