DoS after non-blocking IO error
- 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 10.0.5, 9.0.45, 8.5.65
- 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
Summary
A vulnerability in Apache Tomcat allows an attacker to remotely trigger a denial of service. An error introduced as part of a change to improve error handling during non-blocking I/O meant that the error flag associated with the Request object was not reset between requests. This meant that once a non-blocking I/O error occurred, all future requests handled by that request object would fail. Users were able to trigger non-blocking I/O errors, e.g. by dropping a connection, thereby creating the possibility of triggering a DoS. Applications that do not use non-blocking I/O are not exposed to this vulnerability. This issue affects Apache Tomcat 10.0.3 to 10.0.4; 9.0.44; 8.5.64.
Timeline
- CVE published
- Record last updated
Affected versions
- Apache Software Foundation Apache Tomcat
Apache Tomcat 10 10.0.3 to 10.0.4, Apache Tomcat 9 9.0.44, Apache Tomcat 8.5 8.5.64
- org.apache.tomcat:tomcatMaven
From 10.0.3 · fixed in 10.0.5
- org.apache.tomcat:tomcatMaven
From 9.0.0 · fixed in 9.0.45
- org.apache.tomcat:tomcatMaven
fixed in 8.5.65