Описание
The JK Connector (aka mod_jk) 1.2.0 through 1.2.26 in Apache Tomcat allows remote attackers to obtain sensitive information via an arbitrary request from an HTTP client, in opportunistic circumstances involving (1) a request from a different client that included a Content-Length header but no POST data or (2) a rapid series of requests, related to noncompliance with the AJP protocol's requirements for requests containing Content-Length headers.
| Релиз | Статус | Примечание |
|---|---|---|
| dapper | ignored | end of life |
| devel | not-affected | 1:1.2.26-2.1 |
| hardy | ignored | end of life |
| intrepid | released | 1:1.2.26-2+lenny1build0.8.10.1 |
| jaunty | released | 1:1.2.26-2+lenny1build0.9.04.1 |
| karmic | not-affected | 1:1.2.26-2.1 |
| lucid | not-affected | 1:1.2.26-2.1 |
| maverick | not-affected | 1:1.2.26-2.1 |
| natty | not-affected | 1:1.2.26-2.1 |
| oneiric | not-affected | 1:1.2.26-2.1 |
Показывать по
EPSS
2.6 Low
CVSS2
Связанные уязвимости
The JK Connector (aka mod_jk) 1.2.0 through 1.2.26 in Apache Tomcat allows remote attackers to obtain sensitive information via an arbitrary request from an HTTP client, in opportunistic circumstances involving (1) a request from a different client that included a Content-Length header but no POST data or (2) a rapid series of requests, related to noncompliance with the AJP protocol's requirements for requests containing Content-Length headers.
The JK Connector (aka mod_jk) 1.2.0 through 1.2.26 in Apache Tomcat allows remote attackers to obtain sensitive information via an arbitrary request from an HTTP client, in opportunistic circumstances involving (1) a request from a different client that included a Content-Length header but no POST data or (2) a rapid series of requests, related to noncompliance with the AJP protocol's requirements for requests containing Content-Length headers.
The JK Connector (aka mod_jk) 1.2.0 through 1.2.26 in Apache Tomcat al ...
The JK Connector (aka mod_jk) 1.2.0 through 1.2.26 in Apache Tomcat allows remote attackers to obtain sensitive information via an arbitrary request from an HTTP client, in opportunistic circumstances involving (1) a request from a different client that included a Content-Length header but no POST data or (2) a rapid series of requests, related to noncompliance with the AJP protocol's requirements for requests containing Content-Length headers.
EPSS
2.6 Low
CVSS2