Homepage

Directory Traversal Affecting jbcs-httpd24-httpd-manual package, versions <0:2.4.29-35.jbcs.el7

Severity

 Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

Exploit Maturity
Proof of concept
EPSS
95.76% (100th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Directory Traversal vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-JBCSHTTPD24HTTPDMANUAL-3621511
  • published26 Mar 2023
  • disclosed31 Oct 2018
Report a new vulnerability Found a mistake?

Introduced: 31 Oct 2018

CVE-2018-11759  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

Upgrade RHEL:7 jbcs-httpd24-httpd-manual to version 0:2.4.29-35.jbcs.el7 or higher.
This issue was patched in RHSA-2019:0367.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jbcs-httpd24-httpd-manual package and not the jbcs-httpd24-httpd-manual package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

References