# CVE-2007-5342: JULI logging component in Apache Tomcat does not restrict certain permissions for web applications

> Attackers can modify logging configurations and overwrite arbitrary files due to insufficient permission restrictions in the default JULI policy.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w65j-cmqc-37p2

## What is CVE-2007-5342?

CVE-2007-5342 is a medium-severity missing authorization vulnerability in Apache Tomcat, published on 27 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The default catalina.policy in the JULI logging component in Apache Tomcat 5.5.9 through 5.5.25 and 6.0.0 through 6.0.15 does not restrict certain permissions for web applications, which allows attackers to modify logging configuration options and overwrite arbitrary files, as demonstrated by changing the (1) level, (2) directory, and (3) prefix attributes in the org.apache.juli.FileHandler handler.

Weakness: CWE-264

## Which versions are affected by CVE-2007-5342?

4 open source packages ship an affected version, including org.apache.tomcat:tomcat-juli. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat:tomcat-juli` | Maven | From 5.5.9 to 5.5.25 | None |
| `org.apache.tomcat:tomcat-juli` | Maven | From 5.5.9 to 5.5.25 | None |
| `org.apache.tomcat:tomcat-juli` | Maven | From 6.0.0 to 6.0.15 | None |
| `org.apache.tomcat:tomcat-juli` | Maven | From 6.0.0 to 6.0.15 | None |

Products: Apache Tomcat.

## How do I fix CVE-2007-5342?

Upgrade to a fixed version.

## Is CVE-2007-5342 being exploited?

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

## Other vulnerabilities in Apache Tomcat

- [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild)
- [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5342 and fix it if it is affected.

What it is: CVE-2007-5342 is a medium-severity missing authorization vulnerability in Apache Tomcat, published on 27 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-5342 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomcat:tomcat-juli (Maven): affected from 5.5.9 up to 5.5.25; no fix listed
- org.apache.tomcat:tomcat-juli (Maven): affected from 5.5.9 up to 5.5.25; no fix listed
- org.apache.tomcat:tomcat-juli (Maven): affected from 6.0.0 up to 6.0.15; no fix listed
- org.apache.tomcat:tomcat-juli (Maven): affected from 6.0.0 up to 6.0.15; no fix listed

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-2007-5342/ (Markdown: https://insights.sbomify.com/CVE-2007-5342/index.md)
```

## Sources

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

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