Apache Tomcat JK Connector Vulnerability in libapache-mod-jk: Path Normalization Flaw

libapache-mod-jk Updated 02 Oct 2025

Summary

31/10/2018
N/A
Yes i
High
7.5

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. Affects libapache-mod-jk versions < 1:1.2.46-1. Fixed in 1:1.2.46-1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

libapache-mod-jk is a connector module for the Apache Web Server that allows it to communicate with Apache Tomcat. This module is essential for integrating web applications running on Tomcat with the Apache HTTP Server, enabling features like load balancing and reverse proxying. However, it has been found to have a vulnerability that affects how it normalizes requested paths, potentially exposing unintended application functionality.

Vulnerability Detail

The vulnerability, identified as CVE-2018-11759, arises from improper handling of path normalization in the Apache Tomcat JK Connector versions 1.2.0 to 1.2.44. This flaw allows specially crafted requests to bypass access controls and expose application functionalities that should not be accessible through the reverse proxy. The issue is particularly concerning when only a subset of URLs is exposed, as it can lead to unauthorized access to sensitive application features.

How To Fix

Minimum fixed version

1:1.2.46-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libapache-mod-jk

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, users can restrict access to the affected URLs in the Apache configuration to mitigate the risk of unauthorized access until the package is updated. This can be done by adding specific access control rules in the httpd.conf file, such as: <Location /sensitive-path> Require all denied </Location>

Conclusion

CVE-2018-11759 represents a significant security vulnerability in the libapache-mod-jk package, which can lead to unauthorized access to application functionalities. It is crucial for users to upgrade to the latest version to mitigate this risk and ensure the security of their applications.

See every vulnerability recorded for libapache-mod-jk →

Share this vulnerability

FAQ

CVE-2018-11759 is a vulnerability in the Apache Tomcat JK Connector that allows unauthorized access to application functionalities through improper path normalization.

The affected versions are libapache-mod-jk versions 1.2.0 to 1.2.44.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The CVSS score for CVE-2018-11759 is 7.5, indicating a high severity level.

If immediate upgrading is not possible, implement access control measures in your Apache configuration to restrict access to sensitive paths as a temporary workaround.

Related vulnerabilities

Recent vulnerabilities recorded for libapache-mod-jk.

How To Fix

Minimum fixed version

1:1.2.46-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libapache-mod-jk

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback