Apache Tomcat: Client certificate verification bypass due to virtual host mapping
- 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 11.0.15, 10.1.50, 9.0.113
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Improper Input Validation vulnerability. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.14, from 10.1.0-M1 through 10.1.49, from 9.0.0-M1 through 9.0.112. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 through 8.5.100. Older EOL versions are not affected. Tomcat did not validate that the host name provided via the SNI extension was the same as the host name provided in the HTTP host header field. If Tomcat was configured with more than one virtual host and the TLS configuration for one of those hosts did not require client certificate authentication but another one did, it was possible for a client to bypass the client certificate authentication by sending different host names in the SNI extension and the HTTP host header field. The vulnerability only applies if client certificate authentication is only enforced at the Connector. It does not apply if client certificate authentication is enforced at the web application. Users are recommended to upgrade to version 11.0.15 or later, 10.1.50 or later or 9.0.113 or later, which fix the issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Apache Software Foundation Apache Tomcat
From 11.0.0-M1 · through 11.0.14; From 10.1.0-M1 · through 10.1.49; From 9.0.0-M1 · through 9.0.112; From 8.5.0 · through 8.5.100
- org.apache.tomcat.embed:tomcat-embed-coreMaven
From 11.0.0-M1 · fixed in 11.0.15
- org.apache.tomcat.embed:tomcat-embed-coreMaven
From 10.1.0-M1 · fixed in 10.1.50
- org.apache.tomcat.embed:tomcat-embed-coreMaven
From 9.0.0-M1 · fixed in 9.0.113
- org.apache.tomcat:tomcatMaven
From 11.0.0-M1 · fixed in 11.0.15
- org.apache.tomcat:tomcatMaven
From 10.1.0-M1 · fixed in 10.1.50
- org.apache.tomcat:tomcatMaven
From 9.0.0-M1 · fixed in 9.0.113
- org.apache.tomcat:tomcat-coyoteMaven
From 11.0.0-M1 · fixed in 11.0.15
- org.apache.tomcat:tomcat-coyoteMaven
From 10.1.0-M1 · fixed in 10.1.50
- org.apache.tomcat:tomcat-coyoteMaven
From 9.0.0-M1 · fixed in 9.0.113
- org.apache.tomcat.embed:tomcat-embed-coreMaven
From 8.5.0 · through 8.5.100
- org.apache.tomcat:tomcatMaven
From 8.5.0 · through 8.5.100
- org.apache.tomcat:tomcat-coyoteMaven
From 8.5.0 · through 8.5.100