CVE-2007-5342 is an insecure default-permissions vulnerability in the JULI logging component of Apache Tomcat 5.5.9 through 5.5.25 and 6.0.0 through 6.0.15. The default catalina.policy grants web applications permissions that insufficiently restrict JULI logging configuration. An untrusted web application can modify org.apache.juli.FileHandler settings, including its logging level, output directory, and filename prefix, allowing it to direct logging output to arbitrary locations writable by the Tomcat process and overwrite files.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A weak default security-policy vulnerability in Apache Tomcat's JULI logging component. The default catalina.policy grants web applications excessive permissions, enabling an attacker to alter FileHandler logging attributes—including level, directory, and prefix—and overwrite arbitrary files.
Privilege-escalation risk through unrestricted JULI logging configuration.
Third-party software vulnerability addressed by the HP XP P9000 Performance Advisor v5.5.1 update.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.