medium
5
CWE
284
Advisory Published
CVE Published
Updated

CVE-2014-7810

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&amp;revision=1644019">http://svn.apache.org/viewvc?view=revision&amp;revision=1644019</a> <a href="http://svn.apache.org/viewvc?view=revision&amp;revision=1645644">http://svn.apache.org/viewvc?view=revision&amp;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 SoftwareAffected VersionHow 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 Linux=7.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=6.0.39
Tomcat=6.0.41
Tomcat=6.0.43
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
Tomcat=7.0.54
Tomcat=7.0.55
Tomcat=7.0.56
Tomcat=7.0.57
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=8.0.8
Tomcat=8.0.9
Tomcat=8.0.11
Tomcat=8.0.12
Tomcat=8.0.14
Tomcat=8.0.15
HPE HP-UX=11.31

Remedy

http://svn.apache.org/viewvc?view=revision&revision=1644018

Remedy

http://svn.apache.org/viewvc?view=revision&revision=1645642

Remedy

http://tomcat.apache.org/security-6.html

Remedy

http://tomcat.apache.org/security-7.html

Remedy

http://tomcat.apache.org/security-8.html

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2014-7810?

    CVE-2014-7810 has a severity rating that indicates it can be exploited to bypass security manager protections.

  • How do I fix CVE-2014-7810?

    To fix CVE-2014-7810, upgrade to Apache Tomcat versions 6.0.41, 7.0.59, or 8.0.17 or later.

  • What versions of Apache Tomcat are affected by CVE-2014-7810?

    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.

  • Can CVE-2014-7810 be exploited remotely?

    Yes, CVE-2014-7810 can be exploited remotely by malicious web applications.

  • Is there any workaround for CVE-2014-7810?

    There is no known workaround for CVE-2014-7810; upgrading to a patched version is recommended.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203