First published: Mon May 18 2015(Updated: )
It was found that the expression language resolver evaluated expressions within a privileged code section. A malicious web application could use this flaw to bypass security manager protections. Upstream patches: <a href="http://svn.apache.org/viewvc?view=revision&revision=1644019">http://svn.apache.org/viewvc?view=revision&revision=1644019</a> <a href="http://svn.apache.org/viewvc?view=revision&revision=1645644">http://svn.apache.org/viewvc?view=revision&revision=1645644</a> External References: <a href="http://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.44">http://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.44</a> <a href="http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.59">http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.59</a> <a href="http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.17">http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.17</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/tomcat | <8.0.17 | 8.0.17 |
redhat/tomcat | <7.0.59 | 7.0.59 |
redhat/tomcat | <6.0.44 | 6.0.44 |
Debian Debian Linux | =7.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 | =6.0.39 | |
Apache Tomcat | =6.0.41 | |
Apache Tomcat | =6.0.43 | |
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 | |
Apache Tomcat | =7.0.54 | |
Apache Tomcat | =7.0.55 | |
Apache Tomcat | =7.0.56 | |
Apache Tomcat | =7.0.57 | |
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 | =8.0.8 | |
Apache Tomcat | =8.0.9 | |
Apache Tomcat | =8.0.11 | |
Apache Tomcat | =8.0.12 | |
Apache Tomcat | =8.0.14 | |
Apache Tomcat | =8.0.15 | |
HPE HP-UX | =11.31 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-7810 has a severity rating that indicates it can be exploited to bypass security manager protections.
To fix CVE-2014-7810, upgrade to Apache Tomcat versions 6.0.41, 7.0.59, or 8.0.17 or later.
CVE-2014-7810 affects Apache Tomcat versions 6.0.0 to 6.0.41, 7.0.0 to 7.0.59, and 8.0.0 to 8.0.17.
Yes, CVE-2014-7810 can be exploited remotely by malicious web applications.
There is no known workaround for CVE-2014-7810; upgrading to a patched version is recommended.