Apache Tomcat JK Status Manager Access

Febna V M

Published on

10 Jan 2022

Description

In Apache Tomcat JK (mod_jk) Connector 1.2.0 to 1.2.44, the Apache Web Server (httpd) specific code that normalised the requested path before matching it to the URI-worker map did not handle some edge cases correctly. 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 if only a subset of the URLs supported by Tomcat were exposed via httpd. A specially constructed request could also bypass the access controls configured in httpd in some configurations.

Recommendations

Patch is available for mod_jk (version 1.2.46).
Update to the latest version

Automated human-like penetration testing for your web apps & APIs

Teams using Beagle Security are set up in minutes, embrace release-based CI/CD security testing and save up to 65% with timely remediation of vulnerabilities. Sign up for a free account to see what it can do for you.

Product tour

Written by