Apache Tomcat JK Status Manager Access

Febna V M
Published on
10 Jan 2022


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.


  • 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.

Written by
Febna V M
Febna V M
Cyber Security Engineer
Find website security issues in a flash
Improve your website's security posture with proactive vulnerability detection.
Free website security assessment