Tomcat ConnectorsWeb server / proxy · Apache
CVE-2014-8111
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApache Tomcat Connectors (mod_jk) before 1.2.41 ignores JkUnmount rules for subtrees of previous JkMount rules, which allows remote attackers to access otherwise restricted artifacts via unspecified vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Tomcat Connectors (mod_jk) before version 1.2.41 fails to properly enforce JkUnmount directives for URL subtrees that fall under earlier JkMount rules. This allows attackers to access restricted Tomcat resources that should have been unmounted/unexposed through the connector.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Tomcat ConnectorsWeb server / proxy
<= 1.2.40CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm mod_jk is loaded in ApacheInspect your Apache configuration files (httpd.conf, mod_jk.conf, or included files) for a LoadModule directive that loads the mod_jk module (typically 'LoadModule jk_module modules/mod_jk.so')Affected if mod_jk module is loaded and the version is 1.2.40 or earlier
-
Determine installed mod_jk versionRun 'httpd -M' or 'apachectl -M' to list compiled-in modules and check any version information available, or query the mod_jk binary directly if accessible (e.g., 'mod_jk.so --version' or check the file metadata)Affected if The installed version is 1.2.40 or lower
-
Identify JkMount directives in configurationSearch Apache configuration files for 'JkMount' directives and note the URL paths they map to Tomcat applicationsAffected if JkMount rules exist that map URL paths to Tomcat contexts
-
Identify JkUnmount directives in configurationSearch Apache configuration files for 'JkUnmount' directives, particularly looking for patterns where JkUnmount targets URL subtrees under earlier JkMount rulesAffected if JkUnmount directives exist for paths that are subtrees of earlier JkMount mappings (e.g., JkMount /app/* followed by JkUnmount /app/admin)
-
Verify unmount behavior matches intentTest accessing the unmounted sub-path URLs from a browser or curl request to confirm whether they are actually blocked or still accessible despite JkUnmount configurationAffected if Resources that should be unmounted remain accessible, indicating the vulnerability is present
You are affected if mod_jk version 1.2.40 or earlier is installed AND JkMount/JkUnmount configurations exist where unmounted sub-paths are still reachable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade mod_jk to version 1.2.41 or later, then audit existing JkMount/JkUnmount configurations to verify unmount rules are being properly applied.
Fix this in Tomcat Connectors
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8111 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-8111 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data