CVE-2018-8014: Critical severity Apache Tomcat vulnerability

Published May 16, 2018
·
Updated

Apache Tomcat through versions 7.0.88, 8.0.52, 8.5.31 and 9.0.8 have defaults settings for the CORS filter that are insecure and enable 'supportsCredentials' for all origins.

Upstream announcement:

https://lists.apache.org/thread.html/fbfb713e4f8a4c0f81089b89450828011343593800cae3fb629192b1@%3Cannounce.tomcat.apache.org%3E

Upstream bug:

https://bz.apache.org/bugzilla/showbug.cgi?id=62343

Upstream Patches:

http://svn.apache.org/viewvc?view=rev&rev=1831726 / trunk/9.0 http://svn.apache.org/viewvc?view=rev&rev=1831728 / 8.5 http://svn.apache.org/viewvc?view=rev&rev=1831729 / 8.0 http://svn.apache.org/viewvc?view=rev&rev=1831730 / 7.0

External References:

http://tomcat.apache.org/security-9.html#FixedinApacheTomcat9.0.9 http://tomcat.apache.org/security-8.html#FixedinApacheTomcat8.5.32 http://tomcat.apache.org/security-8.html#FixedinApacheTomcat8.0.53 http://tomcat.apache.org/security-7.html#FixedinApacheTomcat7.0.89

Other sources

The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CORS filter will have configured it appropriately for their environment rather than using it in the default configuration. Therefore, it is expected that most users will not be impacted by this issue.

Launchpad

Affected Software

30 affected componentsFixes available
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.0.0RC1<8.0.53
8.0.53
maven/org.apache.tomcat.embed:tomcat-embed-core>=9.0.0.M1<=9.0.8
9.0.9
maven/org.apache.tomcat.embed:tomcat-embed-core>=7.0.41<7.0.88
7.0.88
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.5.0<8.5.32
8.5.32
Apache Tomcat>=7.0.41<=7.0.88
Apache Tomcat>=8.0.0<=8.0.52
Apache Tomcat>=8.5.0<=8.5.31
Apache Tomcat>=9.0.0<=9.0.8
Apache Tomcat=8.0.0-rc1
Apache Tomcat=9.0.0-milestone1
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=17.10
Canonical Ubuntu Linux=18.04
Debian Debian Linux=8.0
NetApp OnCommand Insight
NetApp Oncommand Unified Manager Vmware Vsphere>=9.4
NetApp OnCommand Workflow Automation
NetApp SnapCenter Server
NetApp Storage Automation Store
All of the following
NetApp OnCommand Unified Manager>=7.3
Microsoft Windows
Apache Tomcat=9.0.0-m1
NetApp OnCommand Unified Manager>=7.3
Microsoft Windows
redhat/tomcat<8.0.53
8.0.53
redhat/tomcat<8.5.32
8.5.32
redhat/tomcat<9.0.9
9.0.9
redhat/tomcat<7.0.89
7.0.89
debian/tomcat9
9.0.43-2~deb11u109.0.118-0+deb11u19.0.70-29.0.95-19.0.118-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 8.0.53
  2. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 9.0.9
  3. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 7.0.88
  4. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 8.5.32
  5. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.0.53
  6. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.32
  7. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.9
  8. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 7.0.89
  9. Upgrade

    Upgrade debian/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.43-2~deb11u10Fixed in 9.0.118-0+deb11u1Fixed in 9.0.70-2Fixed in 9.0.95-1Fixed in 9.0.118-1
  10. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 7.0.89
  11. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 8.0.53
  12. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.32
  13. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.9
  14. Configuration

    Update the CORS filter configuration so it does not enable 'supportsCredentials' for all origins (use an explicit, environment-appropriate CORS configuration rather than the insecure defaults).

    Apache Tomcat CORS filter supportsCredentials = false

Event History

May 16, 2018
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Data Sourced
via NVD·04:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 18, 2018
Data Sourced
via Red Hat·03:29 AM
DescriptionSeverityAffected Software
Oct 17, 2018
Advisory Published
via GitHub·04:32 PM
Aug 25, 2025
Data Sourced
via Ubuntu·12:06 AM
RemedyDescriptionSeverityAffected Software
Sep 22, 2025
Data Sourced
via Launchpad·12:10 AM
Description
Jun 7, 2026
Data Sourced
via Debian·09:27 AM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2018-8014?

CVE-2018-8014 is a vulnerability that affects the default settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.41 to 7.0.88.

2

What is the severity of CVE-2018-8014?

CVE-2018-8014 has a severity rating of 9.8 out of 10.

3

How does CVE-2018-8014 impact Apache Tomcat?

CVE-2018-8014 affects the CORS filter in Apache Tomcat and allows the 'supportsCredentials' option to be enabled for all origins, which can lead to insecure configurations.

4

How can I fix CVE-2018-8014?

To fix CVE-2018-8014, it is recommended to upgrade Apache Tomcat to version 9.0.9, 8.5.32, or 8.0.53, depending on your installed version.

5

Where can I find more information about CVE-2018-8014?

You can find more information about CVE-2018-8014 in the references provided: [link1], [link2], [link3].

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