LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1304: The URL pattern of "" (the empty string) which exactly maps to the context root was not correctly handled i...

The URL pattern of "" (the empty string) which exactly maps to the context root was not correctly handled in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 when used as part of a security constraint definition. This caused the constraint to be ignored. It was, therefore, possible for unauthorised users to gain access to web application resources that should have been protected. Only security constraints with a URL pattern of the empty string were affected.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Apache Tomcat could ignore a protection rule for the application root when the rule used the empty-string URL pattern. In affected versions, unauthorized users might reach web application resources intended to be protected. Exposure depends on applications using that specific security-constraint pattern. Organizations are most exposed if they run the listed Tomcat versions and deploy applications with web security constraints for the context root using the empty-string URL pattern. Tomcat deployments without that specific constraint pattern are not indicated as affected by the provided description. Treat as a targeted configuration-dependent access-control issue. Prioritize systems hosting sensitive applications on affected Tomcat versions, especially externally reachable services. Urgency is lower than a broadly exploitable remote-code issue, but protected content exposure can still carry business impact. Mitigation focus: Inventory Apache Tomcat versions across internet-facing and internal applications.; Prioritize upgrades or vendor package updates for versions in the affected ranges.; Review vendor advisories from Apache, Red Hat, Debian, Ubuntu, Oracle, and NetApp as applicable..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-1304 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
37Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache TomcatApache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49, 7.0.0 to 7.0.84Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.