| Package | Affected versions | Patched versions |
|---|---|---|
| libxml2 | = 1.7.0= 1.7.1= 1.7.2= 1.7.3= 1.7.4= 1.8.0= 1.8.1= 1.8.10= 1.8.13= 1.8.14= 1.8.16= 1.8.2= 1.8.3= 1.8.4= 1.8.5= 1.8.6= 1.8.7= 1.8.9= 2.0.0= 2.1.0= 2.1.1= 2.2.0= 2.2.1= 2.2.10= 2.2.11= 2.2.2= 2.2.3= 2.2.4= 2.2.5= 2.2.6= 2.2.7= 2.2.8= 2.2.9= 2.3.0= 2.3.1= 2.3.10= 2.3.11= 2.3.12= 2.3.13= 2.3.14= 2.3.2= 2.3.3= 2.3.4= 2.3.5= 2.3.6= 2.3.7= 2.3.8= 2.3.9= 2.4.1= 2.4.10= 2.4.11= 2.4.12= 2.4.13= 2.4.14= 2.4.15= 2.4.16= 2.4.17= 2.4.18= 2.4.19= 2.4.2= 2.4.20= 2.4.21= 2.4.22= 2.4.23= 2.4.24= 2.4.25= 2.4.26= 2.4.27= 2.4.28= 2.4.29= 2.4.3= 2.4.30= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9= 2.5.0= 2.5.10= 2.5.11= 2.5.4= 2.5.7= 2.5.8= 2.6.0= 2.6.1= 2.6.11= 2.6.12= 2.6.13= 2.6.14= 2.6.16= 2.6.17= 2.6.18= 2.6.2= 2.6.20= 2.6.21= 2.6.22 |
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free= 2.6.23= 2.6.24= 2.6.25= 2.6.26= 2.6.27= 2.6.28= 2.6.29= 2.6.3= 2.6.30= 2.6.31= 2.6.32= 2.6.4= 2.6.5= 2.6.6= 2.6.7= 2.6.8= 2.6.9= 2.7.0= 2.7.1= 2.7.2= 2.7.3= 2.7.4= 2.7.5= 2.7.6= 2.7.7= 2.7.8= 2.8.0= 2.9.0≤ 2.9.1