CVE-2014-0119: Medium severity Apache Tomcat vulnerability

Published 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.

Other sources

It was found that in limited circumstances it was possible for a malicious web application to replace the XML parsers used by Tomcat to process XSLTs for the default servlet, JSP documents, tag library descriptors (TLDs) and tag plugin configuration files. The injected XML parser(s) could then bypass the limits imposed on XML external entities and/or have visibility of the XML files processed for other web applications deployed on the same Tomcat instance.

Red Hat

Affected Software

121 affected componentsFixes available
redhat/tomcat<7.0.54
7.0.54
redhat/tomcat<6.0.41
6.0.41
redhat/jbossweb<7.4.7.
7.4.7.
Apache Tomcat=8.0.0-rc1
Apache Tomcat=8.0.0-rc10
Apache Tomcat=8.0.0-rc2
Apache Tomcat=8.0.0-rc5
Apache Tomcat=8.0.1
Apache Tomcat=8.0.3
Apache Tomcat=8.0.5
Apache Tomcat<=6.0.39
Apache Tomcat=6
Apache Tomcat=6.0
Apache Tomcat=6.0.0
Apache Tomcat=6.0.0-alpha
Apache Tomcat=6.0.1
Apache Tomcat=6.0.1-alpha
Apache Tomcat=6.0.2
Apache Tomcat=6.0.2-alpha
Apache Tomcat=6.0.2-beta
Apache Tomcat=6.0.3
Apache Tomcat=6.0.4
Apache Tomcat=6.0.4-alpha
Apache Tomcat=6.0.5
Apache Tomcat=6.0.6
Apache Tomcat=6.0.6-alpha
Apache Tomcat=6.0.7
Apache Tomcat=6.0.7-alpha
Apache Tomcat=6.0.7-beta
Apache Tomcat=6.0.8
Apache Tomcat=6.0.8-alpha
Apache Tomcat=6.0.9
Apache Tomcat=6.0.9-beta
Apache Tomcat=6.0.10
Apache Tomcat=6.0.11
Apache Tomcat=6.0.12
Apache Tomcat=6.0.13
Apache Tomcat=6.0.14
Apache Tomcat=6.0.15
Apache Tomcat=6.0.16
Apache Tomcat=6.0.17
Apache Tomcat=6.0.18
Apache Tomcat=6.0.19
Apache Tomcat=6.0.20
Apache Tomcat=6.0.24
Apache Tomcat=6.0.26
Apache Tomcat=6.0.27
Apache Tomcat=6.0.28
Apache Tomcat=6.0.29
Apache Tomcat=6.0.30
Apache Tomcat=6.0.31
Apache Tomcat=6.0.32
Apache Tomcat=6.0.33
Apache Tomcat=6.0.35
Apache Tomcat=6.0.36
Apache Tomcat=6.0.37
Apache Tomcat=7.0.0
Apache Tomcat=7.0.0-beta
Apache Tomcat=7.0.1
Apache Tomcat=7.0.2
Apache Tomcat=7.0.2-beta
Apache Tomcat=7.0.3
Apache Tomcat=7.0.4
Apache Tomcat=7.0.4-beta
Apache Tomcat=7.0.5
Apache Tomcat=7.0.6
Apache Tomcat=7.0.7
Apache Tomcat=7.0.8
Apache Tomcat=7.0.9
Apache Tomcat=7.0.10
Apache Tomcat=7.0.11
Apache Tomcat=7.0.12
Apache Tomcat=7.0.13
Apache Tomcat=7.0.14
Apache Tomcat=7.0.15
Apache Tomcat=7.0.16
Apache Tomcat=7.0.17
Apache Tomcat=7.0.18
Apache Tomcat=7.0.19
Apache Tomcat=7.0.20
Apache Tomcat=7.0.21
Apache Tomcat=7.0.22
Apache Tomcat=7.0.23
Apache Tomcat=7.0.24
Apache Tomcat=7.0.25
Apache Tomcat=7.0.26
Apache Tomcat=7.0.27
Apache Tomcat=7.0.28
Apache Tomcat=7.0.29
Apache Tomcat=7.0.30
Apache Tomcat=7.0.31
Apache Tomcat=7.0.32
Apache Tomcat=7.0.33
Apache Tomcat=7.0.34
Apache Tomcat=7.0.35
Apache Tomcat=7.0.36
Apache Tomcat=7.0.37
Apache Tomcat=7.0.38
Apache Tomcat=7.0.39
Apache Tomcat=7.0.40
Apache Tomcat=7.0.41
Apache Tomcat=7.0.42
Apache Tomcat=7.0.43
Apache Tomcat=7.0.44
Apache Tomcat=7.0.45
Apache Tomcat=7.0.46
Apache Tomcat=7.0.47
Apache Tomcat=7.0.48
Apache Tomcat=7.0.49
Apache Tomcat=7.0.50
Apache Tomcat=7.0.52
Apache Tomcat=7.0.53
maven/org.apache.tomcat:tomcat-jasper>=8.0.0<8.0.6
8.0.6
maven/org.apache.tomcat:tomcat-jasper>=7.0.0<7.0.54
7.0.54
maven/org.apache.tomcat:tomcat-jasper<6.0.40
6.0.40
maven/org.apache.tomcat:tomcat-catalina>=8.0.0<8.0.6
8.0.6
maven/org.apache.tomcat:tomcat-catalina>=7.0.0<7.0.54
7.0.54
maven/org.apache.tomcat:tomcat-catalina<6.0.40
6.0.40
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

Event History

May 31, 2014
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
May 14, 2022
Advisory Published
via GitHub·01:10 AM
Data Sourced
via GitHub·01:10 AM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2014-0119?

CVE-2014-0119 is considered a medium severity vulnerability due to its potential to allow remote attackers to read arbitrary files.

2

How do I fix CVE-2014-0119?

To fix CVE-2014-0119, upgrade Apache Tomcat to version 6.0.40, 7.0.54, or 8.0.6 or later.

3

Which versions of Tomcat are affected by CVE-2014-0119?

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.

4

Can CVE-2014-0119 lead to information disclosure?

Yes, CVE-2014-0119 can lead to information disclosure as it allows unauthorized access to arbitrary files on the server.

5

What types of attacks can exploit CVE-2014-0119?

CVE-2014-0119 can be exploited through crafted web applications that provide an XML external entity, leading to file reading attacks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203