Количество 12
Количество 12
BDU:2019-00886
Уязвимость коннектора Apache Tomcat JK (mod_jk) Connector веб-сервера Apache для движка сервлетов Tomcat Java, связанная с некорректной обработкой граничных условий, позволяющая нарушителю обойти установленный контроль доступа
CVE-2018-11759
The Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map in Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44 did not handle some edge cases correctly. If only a sub-set of the URLs supported by Tomcat were exposed via httpd, then it was possible for a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing the application via the reverse proxy. It was also possible in some configurations for a specially constructed request to bypass the access controls configured in httpd. While there is some overlap between this issue and CVE-2018-1323, they are not identical.
CVE-2018-11759
The Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map in Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44 did not handle some edge cases correctly. If only a sub-set of the URLs supported by Tomcat were exposed via httpd, then it was possible for a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing the application via the reverse proxy. It was also possible in some configurations for a specially constructed request to bypass the access controls configured in httpd. While there is some overlap between this issue and CVE-2018-1323, they are not identical.
CVE-2018-11759
The Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map in Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44 did not handle some edge cases correctly. If only a sub-set of the URLs supported by Tomcat were exposed via httpd, then it was possible for a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing the application via the reverse proxy. It was also possible in some configurations for a specially constructed request to bypass the access controls configured in httpd. While there is some overlap between this issue and CVE-2018-1323, they are not identical.
CVE-2018-11759
The Apache Web Server (httpd) specific code that normalised the reques ...
openSUSE-SU-2018:4032-1
Security update for apache2-mod_jk
SUSE-SU-2023:4513-1
Security update for apache2-mod_jk
SUSE-SU-2018:3969-1
Security update for apache2-mod_jk
SUSE-SU-2018:3963-2
Security update for apache2-mod_jk
SUSE-SU-2018:3963-1
Security update for apache2-mod_jk
GHSA-5q2c-33mg-8m75
The Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map in Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44 did not handle some edge cases correctly. If only a sub-set of the URLs supported by Tomcat were exposed via httpd, then it was possible for a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing the application via the reverse proxy. It was also possible in some configurations for a specially constructed request to bypass the access controls configured in httpd. While there is some overlap between this issue and CVE-2018-1323, they are not identical.
SUSE-SU-2018:3970-1
Security update for apache2-mod_jk
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | BDU:2019-00886 Уязвимость коннектора Apache Tomcat JK (mod_jk) Connector веб-сервера Apache для движка сервлетов Tomcat Java, связанная с некорректной обработкой граничных условий, позволяющая нарушителю обойти установленный контроль доступа | CVSS3: 7.5 | 91% Критический | около 8 лет назад |
 | CVE-2018-11759 The Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map in Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44 did not handle some edge cases correctly. If only a sub-set of the URLs supported by Tomcat were exposed via httpd, then it was possible for a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing the application via the reverse proxy. It was also possible in some configurations for a specially constructed request to bypass the access controls configured in httpd. While there is some overlap between this issue and CVE-2018-1323, they are not identical. | CVSS3: 7.5 | 91% Критический | почти 8 лет назад |
 | CVE-2018-11759 The Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map in Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44 did not handle some edge cases correctly. If only a sub-set of the URLs supported by Tomcat were exposed via httpd, then it was possible for a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing the application via the reverse proxy. It was also possible in some configurations for a specially constructed request to bypass the access controls configured in httpd. While there is some overlap between this issue and CVE-2018-1323, they are not identical. | CVSS3: 7.5 | 91% Критический | почти 8 лет назад |
 | CVE-2018-11759 The Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map in Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44 did not handle some edge cases correctly. If only a sub-set of the URLs supported by Tomcat were exposed via httpd, then it was possible for a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing the application via the reverse proxy. It was also possible in some configurations for a specially constructed request to bypass the access controls configured in httpd. While there is some overlap between this issue and CVE-2018-1323, they are not identical. | CVSS3: 7.5 | 91% Критический | почти 8 лет назад |
| CVE-2018-11759 The Apache Web Server (httpd) specific code that normalised the reques ... | CVSS3: 7.5 | 91% Критический | почти 8 лет назад |
 | openSUSE-SU-2018:4032-1 Security update for apache2-mod_jk | 91% Критический | больше 7 лет назад | |
| SUSE-SU-2023:4513-1 Security update for apache2-mod_jk | 91% Критический | почти 3 года назад | |
| SUSE-SU-2018:3969-1 Security update for apache2-mod_jk | 91% Критический | больше 7 лет назад | |
| SUSE-SU-2018:3963-2 Security update for apache2-mod_jk | 91% Критический | около 7 лет назад | |
| SUSE-SU-2018:3963-1 Security update for apache2-mod_jk | 91% Критический | больше 7 лет назад | |
| GHSA-5q2c-33mg-8m75 The Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map in Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44 did not handle some edge cases correctly. If only a sub-set of the URLs supported by Tomcat were exposed via httpd, then it was possible for a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing the application via the reverse proxy. It was also possible in some configurations for a specially constructed request to bypass the access controls configured in httpd. While there is some overlap between this issue and CVE-2018-1323, they are not identical. | CVSS3: 7.5 | 91% Критический | больше 4 лет назад |
| SUSE-SU-2018:3970-1 Security update for apache2-mod_jk | больше 7 лет назад |
Уязвимостей на страницу