CVE-2021-43980GHSA-JX7C-7MJ5-9438BIT-TOMCAT-2021-43980
Apache Tomcat: Information disclosure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.5.78, 9.0.62, 10.0.20, 10.1.0-M14
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The simplified implementation of blocking reads and writes introduced in Tomcat 10 and back-ported to Tomcat 9.0.47 onwards exposed a long standing (but extremely hard to trigger) concurrency bug in Apache Tomcat 10.1.0 to 10.1.0-M12, 10.0.0-M1 to 10.0.18, 9.0.0-M1 to 9.0.60 and 8.5.0 to 8.5.77 that could cause client connections to share an Http11Processor instance resulting in responses, or part responses, to be received by the wrong client.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Apache Software Foundation Apache Tomcat
10.1.0-M1 to 10.1.0-M12, 10.0.0-M1 to 10.0.18, 9.0.0-M1 to 9.0.60, 8.5.0 to 8.5.77
- org.apache.tomcat:tomcatMaven
From 8.5.0 · fixed in 8.5.78
- org.apache.tomcat:tomcatMaven
From 9.0.0-M1 · fixed in 9.0.62
- org.apache.tomcat:tomcatMaven
From 10.0.0-M1 · fixed in 10.0.20
- org.apache.tomcat:tomcatMaven
From 10.1.0-M1 · fixed in 10.1.0-M14