CVE-2007-5342 — tomcat-juli
CVE-2007-5342 is a CWE-264 vulnerability in org.apache.tomcat:tomcat-juli. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
JULI logging component in Apache Tomcat does not restrict certain permissions for web applications
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
org.apache.tomcat:tomcat-juli☕org.apache.tomcat:tomcat-juliReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat:tomcat-juli | ≥ 5.5.9 | No fix |
| ☕Maven | org.apache.tomcat:tomcat-juli | ≥ 6.0.0 | No fix |
Affected Products
tomcatapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-juli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.apache.tomcat:tomcat-juli for CVE-2007-5342. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| JBEAP 4.2.0 for RHEL 4 | glassfish-javamail-0:1.4.0-0jpp.ep1.10.el4 | RHSA-2008:0833 |
| JBEAP 4.2.0 for RHEL 5 | hibernate3-1:3.2.4-1.SP1_CP04.0jpp.ep1.3.el5 | RHSA-2008:0834 |
| Red Hat Developer Suite V.3 | tomcat5-0:5.5.23-0jpp_11rh | RHSA-2008:0195 |
| Red Hat Enterprise Linux 5 | tomcat5-0:5.5.23-0jpp.3.0.3.el5_1 | RHSA-2008:0042 |
| Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 4 | glassfish-javamail-0:1.4.0-0jpp.ep1.10.el4 | RHSA-2008:0831 |
| Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 5 | glassfish-jaf-0:1.1.0-0jpp.ep1.12.el5.1 | RHSA-2008:0832 |
| RHAPS Version 2 for RHEL 4 | tomcat5-0:5.5.23-0jpp_4rh.9 | RHSA-2008:0862 |
Frequently Asked Questions
Is CVE-2007-5342 in your dependencies?
Find it across Maven, including transitive dependencies.