GHSA-r4x2-3cq5-hqvp CVE-2018-8014

The defaults settings for the CORS filter provided in Apache Tomcat are insecure and enable 'supportsCredentials' for all origins

Critical Maven

Severity: 9.8 / 10; Critical · CVSS 3.0
Exploit chance (EPSS): 20.94%; Chance of exploitation in the next 30 days. Higher than 97.56% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-1188 Initialization of a Resource with an Insecure Default
Fix: 9.0.9; Upgrade org.apache.tomcat.embed:tomcat-embed-core to this version or later

Description

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.

Affected versions

Maven

Package	Vulnerable	Fixed in
org.apache.tomcat.embed:tomcat-embed-core	`>= 9.0.0.M1, < 9.0.9`	`9.0.9`
org.apache.tomcat.embed:tomcat-embed-core	`>= 8.5.0, < 8.5.32`	`8.5.32`
org.apache.tomcat.embed:tomcat-embed-core	`>= 8.0.0RC1, < 8.0.53`	`8.0.53`
org.apache.tomcat.embed:tomcat-embed-core	`>= 7.0.41, < 7.0.88`	`7.0.88`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.tomcat.embed:tomcat-embed-core Maven → `9.0.9`

maven

<dependency><groupId>org.apache.tomcat.embed</groupId><artifactId>tomcat-embed-core</artifactId><version>9.0.9</version></dependency>

gradle

implementation("org.apache.tomcat.embed:tomcat-embed-core:9.0.9")

Severity breakdown

CVSS 3.0 9.8

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

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Weakness

CWE-1188: Initialization of a Resource with an Insecure Default

The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.

References

Advisories

Packages

github.com/apache/tomcat

Timeline

Oct 17, 2018 Published
Mar 12, 2024 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-83qj-6fr2-vhqg Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUT	Critical Known exploited	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-qppj-fm5r-hxr3 HTTP/2 Stream Cancellation Attack	Medium Known exploited	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-xjgh-84hx-56c5 Unrestricted Upload of File with Dangerous Type Apache Tomcat	High Known exploited	Also affects org.apache.tomcat.embed:tomcat-embed-core
CVE-2020-1938 Improper Privilege Management in Tomcat	Critical Known exploited	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-pjfr-qf3p-3q25 When running Apache Tomcat on Windows with HTTP PUTs enabled it was possible to upload a JSP file to the server	High Known exploited	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-h3x4-894j-xpx5 Apache Tomcat's FORM authentication process has an Incorrect Authorization vulnerability	Critical	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-9xv2-5v5q-p794 Apache Tomcat's DIGEST authenticator has an Authentication Bypass by Capture-replay vulnerability	Critical	Also affects org.apache.tomcat.embed:tomcat-embed-core
GHSA-f525-44xv-f2qj Apache Tomcat - HTTP/2 no-authority bypass of strict SNI validation	Critical	Also affects org.apache.tomcat.embed:tomcat-embed-core

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor