dbcve.org
TomcatWeb server / proxy · Apache

CVE-2018-8014

CRITICAL · 9.8 CVSS v3.0 Published 2018-05-16
Fix available
A fix is available. Upgrade to after 9.0.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:>= 7.0.41, <= 7.0.88>= 8.0.0, <= 8.0.52>= 8.5.0, <= 8.5.31>= 9.0.0, <= 9.0.8= 8.0.0= 9.0.0
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 17.10= 18.04
Debian LinuxOperating system
Affected:= 8.0
Oncommand InsightApplication
Affected:all versions
Oncommand Unified ManagerApplication
Affected:>= 9.4>= 7.3
Oncommand Workflow AutomationApplication
Affected:all versions
Snapcenter ServerApplication
Affected:all versions
Storage Automation StoreApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 9.0.8
Vendor patch www.oracle.com →
Recommended fix High confidence

Tomcat 9.0.9 or later; Tomcat 8.5.32 or later; Tomcat 8.0.53 or later; Tomcat 7.0.89 or later

  1. 1. Identify all Tomcat instances running affected versions (7.0.41-7.0.88, 8.0.0-8.0.52, 8.5.0-8.5.31, 9.0.0-9.0.8) in your environment
  2. 2. For each affected Tomcat installation, locate the CORS filter configuration in the web.xml file (typically in $CATALINA_HOME/conf/web.xml)
  3. 3. If using the default CORS filter configuration, explicitly configure the filter with proper CORS settings: set 'supportsCredentials' to 'false' if not required, or restrict allowed origins using 'allowedOrigins' with specific trusted origins instead of '*'
  4. 4. Alternatively, upgrade Tomcat to a fixed version: Tomcat 9.0.9+, Tomcat 8.5.32+, Tomcat 8.0.53+, or Tomcat 7.0.89+
  5. 5. After upgrading or reconfiguring, restart each Tomcat instance
  6. 6. Verify CORS filter behavior by testing with a browser developer console or curl command to confirm proper origin handling
Caveat Upgrading Tomcat may introduce breaking changes in other components; test thoroughly in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-8014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-8014 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data