Threats / Apache / CVE-2020-1938
CVE-2020-1938
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Apache Tomcat vulnerability
Apache Tomcat improperly trusts AJP connections, allowing attackers with network access to exploit the protocol's elevated trust level and potentially compromise the application.
Verdict
Today item — known-exploited.
An attacker with network access to AJP ports can bypass security controls by leveraging Tomcat's implicit trust in AJP connections, leading to unauthorized access or code execution without requiring valid credentials.
CISA KEV Yes · 2022-03-034EPSS 0.9927 (verify live)5Exploit Weaponized · public PoC6CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
18 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03).
Probability (EPSS)
EPSS 0.9927 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Apache, Tomcat. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 738 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that Tomcat treats AJP connections as inherently trustworthy compared to HTTP connections.
Business
The organization's security model assumes AJP ports are isolated or protected, creating a false sense of security.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I gain network access to the AJP port, either through misconfiguration, lateral movement, or direct exposure.
Business
Network segmentation failures or cloud misconfigurations expose internal protocols to unauthorized parties.
3
Lateral reach — past segmentation narrative 3
Attacker
I send crafted AJP requests that exploit the elevated trust level to bypass authentication or authorization checks.
Business
The application processes untrusted requests as if they originated from trusted infrastructure, compromising data integrity and confidentiality.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05