First published: Wed May 28 2014(Updated: )
Apache Tomcat before 6.0.40, 7.x before 7.0.54, and 8.x before 8.0.6 does not properly constrain the class loader that accesses the XML parser used with an XSLT stylesheet, which allows remote attackers to (1) read arbitrary files via a crafted web application that provides an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue, or (2) read files associated with different web applications on a single Tomcat instance via a crafted web application.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.apache.tomcat:tomcat | >=8.0.0<8.0.6 | 8.0.6 |
maven/org.apache.tomcat:tomcat | >=7.0.0<7.0.54 | 7.0.54 |
maven/org.apache.tomcat:tomcat | <6.0.40 | 6.0.40 |
redhat/tomcat | <7.0.54 | 7.0.54 |
redhat/tomcat | <6.0.41 | 6.0.41 |
redhat/jbossweb | <7.4.7. | 7.4.7. |
Tomcat | =8.0.0-rc1 | |
Tomcat | =8.0.0-rc10 | |
Tomcat | =8.0.0-rc2 | |
Tomcat | =8.0.0-rc5 | |
Tomcat | =8.0.1 | |
Tomcat | =8.0.3 | |
Tomcat | =8.0.5 | |
Tomcat | <=6.0.39 | |
Tomcat | =6 | |
Tomcat | =6.0 | |
Tomcat | =6.0.0 | |
Tomcat | =6.0.0-alpha | |
Tomcat | =6.0.1 | |
Tomcat | =6.0.1-alpha | |
Tomcat | =6.0.2 | |
Tomcat | =6.0.2-alpha | |
Tomcat | =6.0.2-beta | |
Tomcat | =6.0.3 | |
Tomcat | =6.0.4 | |
Tomcat | =6.0.4-alpha | |
Tomcat | =6.0.5 | |
Tomcat | =6.0.6 | |
Tomcat | =6.0.6-alpha | |
Tomcat | =6.0.7 | |
Tomcat | =6.0.7-alpha | |
Tomcat | =6.0.7-beta | |
Tomcat | =6.0.8 | |
Tomcat | =6.0.8-alpha | |
Tomcat | =6.0.9 | |
Tomcat | =6.0.9-beta | |
Tomcat | =6.0.10 | |
Tomcat | =6.0.11 | |
Tomcat | =6.0.12 | |
Tomcat | =6.0.13 | |
Tomcat | =6.0.14 | |
Tomcat | =6.0.15 | |
Tomcat | =6.0.16 | |
Tomcat | =6.0.17 | |
Tomcat | =6.0.18 | |
Tomcat | =6.0.19 | |
Tomcat | =6.0.20 | |
Tomcat | =6.0.24 | |
Tomcat | =6.0.26 | |
Tomcat | =6.0.27 | |
Tomcat | =6.0.28 | |
Tomcat | =6.0.29 | |
Tomcat | =6.0.30 | |
Tomcat | =6.0.31 | |
Tomcat | =6.0.32 | |
Tomcat | =6.0.33 | |
Tomcat | =6.0.35 | |
Tomcat | =6.0.36 | |
Tomcat | =6.0.37 | |
Tomcat | =7.0.0 | |
Tomcat | =7.0.0-beta | |
Tomcat | =7.0.1 | |
Tomcat | =7.0.2 | |
Tomcat | =7.0.2-beta | |
Tomcat | =7.0.3 | |
Tomcat | =7.0.4 | |
Tomcat | =7.0.4-beta | |
Tomcat | =7.0.5 | |
Tomcat | =7.0.6 | |
Tomcat | =7.0.7 | |
Tomcat | =7.0.8 | |
Tomcat | =7.0.9 | |
Tomcat | =7.0.10 | |
Tomcat | =7.0.11 | |
Tomcat | =7.0.12 | |
Tomcat | =7.0.13 | |
Tomcat | =7.0.14 | |
Tomcat | =7.0.15 | |
Tomcat | =7.0.16 | |
Tomcat | =7.0.17 | |
Tomcat | =7.0.18 | |
Tomcat | =7.0.19 | |
Tomcat | =7.0.20 | |
Tomcat | =7.0.21 | |
Tomcat | =7.0.22 | |
Tomcat | =7.0.23 | |
Tomcat | =7.0.24 | |
Tomcat | =7.0.25 | |
Tomcat | =7.0.26 | |
Tomcat | =7.0.27 | |
Tomcat | =7.0.28 | |
Tomcat | =7.0.29 | |
Tomcat | =7.0.30 | |
Tomcat | =7.0.31 | |
Tomcat | =7.0.32 | |
Tomcat | =7.0.33 | |
Tomcat | =7.0.34 | |
Tomcat | =7.0.35 | |
Tomcat | =7.0.36 | |
Tomcat | =7.0.37 | |
Tomcat | =7.0.38 | |
Tomcat | =7.0.39 | |
Tomcat | =7.0.40 | |
Tomcat | =7.0.41 | |
Tomcat | =7.0.42 | |
Tomcat | =7.0.43 | |
Tomcat | =7.0.44 | |
Tomcat | =7.0.45 | |
Tomcat | =7.0.46 | |
Tomcat | =7.0.47 | |
Tomcat | =7.0.48 | |
Tomcat | =7.0.49 | |
Tomcat | =7.0.50 | |
Tomcat | =7.0.52 | |
Tomcat | =7.0.53 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-0119 is considered a medium severity vulnerability due to its potential to allow remote attackers to read arbitrary files.
To fix CVE-2014-0119, upgrade Apache Tomcat to version 6.0.40, 7.0.54, or 8.0.6 or later.
Versions of Apache Tomcat prior to 6.0.40, 7.x before 7.0.54, and 8.x before 8.0.6 are affected by CVE-2014-0119.
Yes, CVE-2014-0119 can lead to information disclosure as it allows unauthorized access to arbitrary files on the server.
CVE-2014-0119 can be exploited through crafted web applications that provide an XML external entity, leading to file reading attacks.