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.
References
Link | Resource |
---|---|
https://lists.apache.org/thread/3jjqbsp6j88b198x5rmg99b1qr8ht3g3 | Mailing List Vendor Advisory |
http://www.openwall.com/lists/oss-security/2022/09/28/1 | Mailing List Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2022/10/msg00029.html | Mailing List Third Party Advisory |
https://www.debian.org/security/2022/dsa-5265 | Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Information
Published : 2022-09-28 07:15
Updated : 2022-11-09 20:00
NVD link : CVE-2021-43980
Mitre link : CVE-2021-43980
JSON object : View
CWE
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Products Affected
debian
- debian_linux
apache
- tomcat