11.0.24
16 years ago
1 months ago
Known vulnerabilities in the org.apache.tomcat:tomcat-coyote package. This does not include vulnerabilities belonging to this package’s dependencies.
Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
org.apache.tomcat:tomcat-coyote is a Tomcat Connectors and HTTP parser. Affected versions of this package are vulnerable to Improper Validation of Syntactic Correctness of Input in the processing of HTTP/2 request headers. An attacker can cause unexpected behavior or potentially compromise the application by sending specially crafted HTTP/2 request headers. How to fix Improper Validation of Syntactic Correctness of Input? Upgrade | [,9.0.118)[10.0.0-M1,10.1.55)[11.0.0-M1,11.0.22) |
org.apache.tomcat:tomcat-coyote is a Tomcat Connectors and HTTP parser. Affected versions of this package are vulnerable to Timing Attack via AJP secret comparison. An attacker can perform a timing side-channel attack to determine whether a guessed secret is correct by sending many authentication attempts directly to the connector and measuring the time taken to compare secrets. How to fix Timing Attack? Upgrade | [,9.0.118)[10.1.0-M1,10.1.55)[11.0.0-M1,11.0.22) |
org.apache.tomcat:tomcat-coyote is a Tomcat Connectors and HTTP parser. Affected versions of this package are vulnerable to Improper Certificate Validation in Note: This is a partial bypass for the vulnerability described in CVE-2025-66614. How to fix Improper Certificate Validation? Upgrade | [9.0.113,9.0.116)[10.1.50,10.1.53)[11.0.15,11.0.20) |
org.apache.tomcat:tomcat-coyote is a Tomcat Connectors and HTTP parser. Affected versions of this package are vulnerable to HTTP Request Smuggling in How to fix HTTP Request Smuggling? Upgrade | [7.0.0,9.0.116)[10.1.0-M1,10.1.53)[11.0.0-M1,11.0.20) |
org.apache.tomcat:tomcat-coyote is a Tomcat Connectors and HTTP parser. Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm which may arise due to improper preservation of the configured cipher preference order. An attacker who can control the ciphers in use and cause an insecure one to be given higher precedence than the configured one, during TLS negotiation, can access sensitive information. How to fix Use of a Broken or Risky Cryptographic Algorithm? Upgrade | [9.0.114,9.0.116)[10.1.51,10.1.53)[11.0.16,11.0.20) |