Apache Tomcat Native, Apache Tomcat: OCSP revocation bypass
Summary
Improper Input Validation vulnerability in Apache Tomcat Native, Apache Tomcat. When using an OCSP responder, Tomcat Native (and Tomcat's FFM port of the Tomcat Native code) did not complete verification or freshness checks on the OCSP response which could allow certificate revocation to be bypassed. This issue affects Apache Tomcat Native: from 1.3.0 through 1.3.4, from 2.0.0 through 2.0.11; Apache Tomcat: from 11.0.0-M1 through 11.0.17, from 10.1.0-M7 through 10.1.51, from 9.0.83 through 9.0.114. The following versions were EOL at the time the CVE was created but are known to be affected: from 1.1.23 through 1.1.34, from 1.2.0 through 1.2.39. Older EOL versions are not affected. Apache Tomcat Native users are recommended to upgrade to versions 1.3.5 or later or 2.0.12 or later, which fix the issue.
What this means
In plain English
Improper Input Validation vulnerability in Apache Tomcat Native, Apache Tomcat. When using an OCSP responder, Tomcat Native (and Tomcat's FFM port of the Tomcat Native code) did not complete verification or freshness checks on the OCSP response which could allow certificate revocation to be bypassed. This issue affects Apache Tomcat Native: from 1.3.0 through 1.3.4, from 2.0.0 through 2.0.11; Apache Tomcat: from 11.0.0-M1 through 11.0.17, from 10.1.0-M7 through 10.1.51, from 9.0.83 through 9.0.114.
Vulnerable items
- Apache Tomcat Native — Apache Tomcat is a Java application server and servlet container used to host web applications.
- Apache Tomcat — Apache Tomcat is a Java application server and servlet container used to host web applications.
Recommended action
Primary action: update to a vendor-listed fixed release: 1.3.5, 2.0.12, 11.0.18, 10.1.52, 9.0.115. Vendor mitigation: Apache Tomcat Native users are recommended to upgrade to versions 1.3.5 or later or 2.0.12 or later, which fix the issue. Apache Tomcat users are recommended to upgrade to versions 11.0.18 or later, 10.1.52 or later or 9.0.115 or later which fix the issue.
Rewritten locally from the scraped official advisory data above; no generative API is used. The vendor advisory is authoritative.
- Apache Tomcat Native 1.1.23 through 1.1.34
- Apache Tomcat Native 1.2.0 through 1.2.39
- Apache Tomcat Native 1.3.0 through 1.3.4
- Apache Tomcat Native 2.0.0 through 2.0.11
- Apache Tomcat 11.0.0-M1 through 11.0.17
- Apache Tomcat 10.1.0-M7 through 10.1.51
- Apache Tomcat 9.0.83 through 9.0.114
Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source
- 1.3.5
- 2.0.12
- 11.0.18
- 10.1.52
- 9.0.115
Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source
Mitigation checklist
- Apache Tomcat Native users are recommended to upgrade to versions 1.3.5 or later or 2.0.12 or later, which fix the issue.
- Apache Tomcat users are recommended to upgrade to versions 11.0.18 or later, 10.1.52 or later or 9.0.115 or later which fix the issue.
Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.