Incomplete CleanupAffected versions of this package are vulnerable to Incomplete Cleanup via handshake-wrap state handling in the SecureNioChannel component. A TLS client can trigger intermittent TLS 1.3 connection failures by sending traffic that leaves a handshake wrap pending; after the channel wraps application data, its handshake-progress flag remains stale, so subsequent handshake processing throws an I/O error and the connection fails.
How to fix Incomplete Cleanup? Upgrade org.apache.tomcat.experimental:tomcat-embed-programmatic to version 9.0.123, 10.1.61, 11.0.27 or higher.
| [9.0.90,9.0.123)[10.1.25,10.1.61)[11.0.0-M21,11.0.27) |
Authentication Bypass by Primary WeaknessAffected versions of this package are vulnerable to Authentication Bypass by Primary Weakness via the getServerAuthConfig method in SimpleAuthConfigProvider. When Jakarta Authentication uses this provider as the default for multiple web applications, its cached configuration retains the realm of the first application to authenticate a request. An attacker can send requests to another application and have them authenticated against that first realm, potentially gaining access to resources protected by the other application’s intended authentication.
How to fix Authentication Bypass by Primary Weakness? Upgrade org.apache.tomcat.experimental:tomcat-embed-programmatic to version 9.0.122, 10.1.60, 11.0.26 or higher.
| [9.0.0.M4,9.0.122)[10.1.0-M1,10.1.60)[11.0.0-M1,11.0.26) |
Incorrect SynchronizationAffected versions of this package are vulnerable to Incorrect Synchronization via the shared header emitter in the HTTP/2 HpackDecoder. An attacker can inject trailer fields into another HTTP/2 request by sending requests that cause a stream to be reset and replaced while headers are being decoded, making the server process the other request with attacker-supplied trailer data.
Notes
- At the decoder-to-request handoff, the affected and attacker-controlled streams must be on the same HTTP/2 connection, whose
HpackDecoder shares the header emitter.
How to fix Incorrect Synchronization? Upgrade org.apache.tomcat.experimental:tomcat-embed-programmatic to version 9.0.122, 10.1.60, 11.0.26 or higher.
| [9.0.39,9.0.122)[10.1.0-M1,10.1.60)[11.0.0-M1,11.0.26) |
HTTP Request SmugglingAffected versions of this package are vulnerable to HTTP Request Smuggling via the Http11Processor in the HTTP/1.x request-processing component. An attacker can cause one request from another user to fail by sending an HTTP/1.0 request with a Transfer-Encoding header when Tomcat is behind a reverse proxy that interprets the request differently.
How to fix HTTP Request Smuggling? Upgrade org.apache.tomcat.experimental:tomcat-embed-programmatic to version 9.0.122, 10.1.60, 11.0.26 or higher.
| [8.5.67,9.0.122)[10.1.0-M1,10.1.60)[11.0.0-M1,11.0.26) |