CVE-2014-0107 is an insufficiently implemented security check in Apache Xalan-Java before 2.7.2. When FEATURE_SECURE_PROCESSING is enabled, TransformerFactory does not adequately restrict certain XSLT and Java system-property-related properties. A crafted XSLT stylesheet can use affected content-header or entities properties, or a Java property bound to the XSLT 1.0 system-property function, to bypass the restrictions expected from secure-processing mode.
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.
22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Xalan-Java insufficient constraints in its secure-processing feature.
A weakness in Xalan-Java secure-processing restrictions that allows attacker-supplied XSLT to bypass constraints and can potentially result in remote code execution, depending on available classpath components.
An Xalan-Java secure-processing bypass affecting applications that process attacker-controlled XSLT. Depending on components in the classpath, exploitation can lead to remote code execution.
An insufficient-restrictions flaw in Xalan-Java secure processing that could allow an attacker-supplied XSLT document to bypass constraints and potentially achieve remote code execution in the application-server context.
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.