Service interruption via persistent request error flag
Published Jul 12, 2021 · Updated Aug 3, 2024
Improper error handling in Apache Tomcat 10.0.3 through 10.0.4, 9.0.44, and 8.5.64 allows remote attackers to interrupt service. The Request object retains its error flag after a non-blocking I/O error, causing later requests assigned to that reused object to fail. Only applications using non-blocking I/O are exposed; dropping a connection can poison a reused Request object and disrupt subsequent traffic.
Summary
What happened
Improper error handling in Apache Tomcat 10.0.3 through 10.0.4, 9.0.44, and 8.5.64 allows remote attackers to interrupt service. The Request object retains its error flag after a non-blocking I/O error, causing later requests assigned to that reused object to fail. Only applications using non-blocking I/O are exposed; dropping a connection can poison a reused Request object and disrupt subsequent traffic.
The record
- CVE
- CVE-2021-30639
- Published
- Jul 12, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Tomcat
- Classifications
- CWE-755, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Apache Tomcat 10 10.0.3 to 10.0.4
- Affected versionversion=Apache Tomcat 8.5 8.5.64
- Affected versionversion=Apache Tomcat 9 9.0.44
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo