CVE-2016-6325 is an improper access control vulnerability in Red Hat-packaged Apache Tomcat. Certain configuration files consumed by the Tomcat initialization script were writable by the tomcat group. A tomcat-group member, including code operating through a malicious application deployed to Tomcat, could modify initialization configuration that is subsequently processed by the service startup mechanism and escalate local privileges. Affected products include Red Hat Enterprise Linux 5 through 7 Tomcat packages, JBoss Web Server 3.0, and JBoss EWS 2.
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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Local privilege-escalation vulnerability due to Tomcat configuration files being writable by the tomcat group.
Tomcat writable configuration files enable local privilege escalation by a tomcat-group member or malicious deployed web application.
A privilege-escalation vulnerability arising from Tomcat configuration files being writable by the tomcat group.
A local privilege-escalation flaw in Tomcat caused by initialization-script configuration files being writable by the tomcat group.
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.