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.
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Link | Tags |
---|---|
https://lists.apache.org/thread/3jjqbsp6j88b198x5rmg99b1qr8ht3g3 | vendor advisory mailing list |
http://www.openwall.com/lists/oss-security/2022/09/28/1 | third party advisory mailing list |
https://lists.debian.org/debian-lts-announce/2022/10/msg00029.html | third party advisory mailing list |
https://www.debian.org/security/2022/dsa-5265 | third party advisory vendor advisory |