LiveActive security incident?Get immediate response
CVE Record

CVE-2018-8020: Apache Tomcat Native 1.2.0 to 1.2.16 and 1.1.23 to 1.1.34 has a flaw that does not properly check OCSP pre-...

Apache Tomcat Native 1.2.0 to 1.2.16 and 1.1.23 to 1.1.34 has a flaw that does not properly check OCSP pre-produced responses, which are lists (multiple entries) of certificate statuses. Subsequently, revoked client certificates may not be properly identified, allowing for users to authenticate with revoked certificates to connections that require mutual TLS. Users not using OCSP checks are not affected by this vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw affects Apache Tomcat Native when mutual TLS depends on OCSP checks to reject revoked client certificates. In affected versions, some pre-produced OCSP responses with multiple certificate-status entries may be mishandled, so a revoked client certificate could still authenticate. Organizations not using OCSP checks are not affected, per the CVE description. Exposure is most likely on Tomcat deployments using Apache Tomcat Native for TLS, requiring mutual TLS, and enabling OCSP checks. Deployments without OCSP checks are stated as unaffected. Evidence does not identify broad internet-wide exposure. Prioritize remediation where mTLS protects sensitive services, partner access, administration, or regulated workflows. For systems without OCSP checks or without client-certificate authentication, business urgency is lower but inventory validation is still warranted. Mitigation focus: Upgrade Apache Tomcat Native outside the affected version ranges using vendor guidance.; Apply relevant OS vendor security updates, including Red Hat or Debian packages where applicable.; Review Tomcat TLS configurations that require client certificates and OCSP revocation checks..

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-8020 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
11Source links

CVSS and timeline data

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

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Tomcat Native1.2.0 to 1.2.16, 1.1.23 to 1.1.34Listed
Weakness

CWE details

No CWE listed

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