Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2014-0107

Xalan-Java: insufficient constraints in secure processing feature

Overview

Published
15 Apr 2014
Modified
6 May 2026
High CVE
1 Registry packages
5 OS packages
3 Linux distributions
Yes Fix available

Description

The TransformerFactory in Apache Xalan-Java before 2.7.2 does not properly restrict access to certain properties when FEATURE_SECURE_PROCESSING is enabled, which allows remote attackers to bypass expected restrictions and load arbitrary classes or access external resources via a crafted (1) xalan:content-header, (2) xalan:entities, (3) xslt:content-header, or (4) xslt:entities property, or a Java property that is bound to the XSLT 1.0 system-property function.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Weakness: CWE-264

Affected packages · 1

Packages affected by CVE-2014-0107
EcosystemPackageVulnerableFixed in
Maven xalan:xalan <2.7.2 2.7.2

Open a package to see all its vulnerabilities.

Operating systems · 6 fixes

debian 4 releases · 1 package

fixed 4
libxalan2-java
debian fixes for CVE-2014-0107
ReleasePackageFixed in
11 libxalan2-java 2.7.1-9
12 libxalan2-java 2.7.1-9
13 libxalan2-java 2.7.1-9
14 libxalan2-java 2.7.1-9

echo 1 release · 1 package

fixed 1
libxalan2-java
echo fixes for CVE-2014-0107
ReleasePackageFixed in
libxalan2-java 2.7.1-9

openSUSE 1 release · 1 package

fixed 1
xalan-j2
openSUSE fixes for CVE-2014-0107
ReleasePackageFixed inAdvisory
Tumbleweed xalan-j2 +3 2.7.2-5.4 openSUSE-SU-2024:10404-1

References

Show all 50 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.