# CVE-2014-8111: Missing authorization in n/a

> Remote attackers can bypass JkUnmount restrictions to access protected artifacts in Apache Tomcat Connectors due to improper rule handling.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-8111, DLA-240-1, DSA-3278-1, GHSA-f49p-9mwv-783f, MGASA-2015-0254

## What is CVE-2014-8111?

CVE-2014-8111 is a medium-severity missing authorization vulnerability in n/a, published on 21 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-8111?

It affects 1 product.


Products: Apache Tomcat Connectors.

## How do I fix CVE-2014-8111?

Upgrade to a fixed version.

## Is CVE-2014-8111 being exploited?

There is no known exploitation of CVE-2014-8111 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-41081](https://insights.sbomify.com/CVE-2023-41081/): Apache Tomcat Connectors: Unexpected use of first declared worker in mod_jk for unmapped request (high 7.5)
- [CVE-2024-46544](https://insights.sbomify.com/CVE-2024-46544/): Apache Tomcat Connectors: mod_jk: local users can view and modify configuration (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8111 and fix it if it is affected.

What it is: CVE-2014-8111 is a medium-severity missing authorization vulnerability in n/a, published on 21 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8111 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-8111/ (Markdown: https://insights.sbomify.com/CVE-2014-8111/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-8111
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-8111
- OSV: https://osv.dev/vulnerability/CVE-2014-8111

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-8111/
Summaries are generated and may contain mistakes; the official description above is the record.