CVE-2014-0107: The TransformerFactory in Apache Xalan-Java before 2.7.2 does not properly restrict access to certain properties when…
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 14% (FIRST EPSS); higher than 96.6% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: libxalan2-java (Debian:12) 2.7.1-9; libxalan2-java (Debian:6.0) 2.7.1-5+deb6u1; libxalan2-java (Debian:7) 2.7.1-7+deb7u1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to libxalan2-java (Debian:12) 2.7.1-9; libxalan2-java (Debian:6.0) 2.7.1-5+deb6u1; libxalan2-java (Debian:7) 2.7.1-7+deb7u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 15, 2014
- Updated
- Jun 16, 2026
- EPSS
- 14.0% · 96th percentile
- CWE
- CWE-264
Report tools
Action score
34
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 14.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | xalan-java | cpe:2.3:a:apache:xalan-java |
| oracle | webcenter sites | cpe:2.3:a:oracle:webcenter_sites |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache xalan-javaup to 2.7.1 inclusive
- apache xalan-java1.0.0
- apache xalan-java2.0.0
- apache xalan-java2.0.1
- apache xalan-java2.1.0
- apache xalan-java2.2.0
- apache xalan-java2.4.0
- apache xalan-java2.4.1
+7 more rows
- apache xalan-java2.5.0
- apache xalan-java2.5.1
- apache xalan-java2.5.2
- apache xalan-java2.6.0
- apache xalan-java2.7.0
- oracle webcenter sites11.1.1.8.0
- oracle webcenter sites7.6.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libxalan2-java | before 2.7.1-9 | 2.7.1-9 |
| Debian:6.0 | libxalan2-java | before 2.7.1-5+deb6u1 | 2.7.1-5+deb6u1 |
| Debian:7 | libxalan2-java | before 2.7.1-7+deb7u1 | 2.7.1-7+deb7u1 |
| Maven | xalan:xalan | before 2.7.2 | 2.7.2 |
| openSUSE:Tumbleweed | xalan-j2 | before 2.7.2-5.4 | 2.7.2-5.4 |
| Red Hat:enterprise_linux:5::client | xalan-j2 | before 0:2.7.0-6jpp.2 | 0:2.7.0-6jpp.2 |
| Red Hat:enterprise_linux:5::client | xalan-j2-debuginfo | before 0:2.7.0-6jpp.2 | 0:2.7.0-6jpp.2 |
| Red Hat:enterprise_linux:5::client | xalan-j2-manual | before 0:2.7.0-6jpp.2 | 0:2.7.0-6jpp.2 |
| Red Hat:enterprise_linux:5::client | xalan-j2-xsltc | before 0:2.7.0-6jpp.2 | 0:2.7.0-6jpp.2 |
| Red Hat:enterprise_linux:5::client_workstation | xalan-j2-demo | before 0:2.7.0-6jpp.2 | 0:2.7.0-6jpp.2 |
| Red Hat:enterprise_linux:5::client_workstation | xalan-j2-javadoc | before 0:2.7.0-6jpp.2 | 0:2.7.0-6jpp.2 |
| Red Hat:enterprise_linux:6::client | xalan-j2 | before 0:2.7.0-9.9.el6_5 | 0:2.7.0-9.9.el6_5 |
| Red Hat:enterprise_linux:6::client | xalan-j2-demo | before 0:2.7.0-9.9.el6_5 | 0:2.7.0-9.9.el6_5 |
| Red Hat:enterprise_linux:6::client | xalan-j2-javadoc | before 0:2.7.0-9.9.el6_5 | 0:2.7.0-9.9.el6_5 |
| Red Hat:enterprise_linux:6::client | xalan-j2-manual | before 0:2.7.0-9.9.el6_5 | 0:2.7.0-9.9.el6_5 |
| Red Hat:enterprise_linux:6::client | xalan-j2-xsltc | before 0:2.7.0-9.9.el6_5 | 0:2.7.0-9.9.el6_5 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | xalan-j2 | before 0:2.7.1-12_patch_08.ep5.el4 | 0:2.7.1-12_patch_08.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el5 | xalan-j2 | before 0:2.7.1-12_patch_08.ep5.el5 | 0:2.7.1-12_patch_08.ep5.el5 |
| Red Hat:jboss_enterprise_application_platform:5::el6 | xalan-j2 | before 0:2.7.1-12_patch_08.ep5.el6 | 0:2.7.1-12_patch_08.ep5.el6 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | xalan-j2-eap6 | before 0:2.7.1-9.redhat_7.1.ep6.el5 | 0:2.7.1-9.redhat_7.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el6 | xalan-j2-eap6 | before 0:2.7.1-9.redhat_7.1.ep6.el6 | 0:2.7.1-9.redhat_7.1.ep6.el6 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-34169Apache Xalan Java XSLT library is vulnerable to an integer truncation issue when processing malicious XSLT stylesheets55Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libxalan2-java | 2.7.1-9 · Debian:12 | Package registry (OSV) |
| Maven:xalan:xalan | 2.7.2 | Package registry (OSV) |
| opensuse:xalan-j2 | 2.7.2-5.4 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:xalan-j2 | 0:2.7.0-6jpp.2 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:xalan-j2-debuginfo | 0:2.7.0-6jpp.2 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:xalan-j2-demo | 0:2.7.0-6jpp.2 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:xalan-j2-eap6 | 0:2.7.1-9.redhat_7.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:xalan-j2-javadoc | 0:2.7.0-6jpp.2 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:xalan-j2-manual | 0:2.7.0-6jpp.2 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:xalan-j2-xsltc | 0:2.7.0-6jpp.2 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-571 · Aug 6, 2020(IBM Ürünleri Güvenlik Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- rhn.redhat.com/errata/RHSA-2014-1351.html
- rhn.redhat.com/errata/RHSA-2015-1888.html
- secunia.com/advisories/57563
- secunia.com/advisories/59036
- secunia.com/advisories/59151
- secunia.com/advisories/59247
- secunia.com/advisories/59290
- secunia.com/advisories/59291
- secunia.com/advisories/59369
- secunia.com/advisories/59515
- secunia.com/advisories/59711
- secunia.com/advisories/60502
- svn.apache.org/viewvc?view=revision&revision=1581058
- www-01.ibm.com/support/docview.wss?uid=swg21674334
- www-01.ibm.com/support/docview.wss?uid=swg21676093
- www-01.ibm.com/support/docview.wss?uid=swg21677145
- www-01.ibm.com/support/docview.wss?uid=swg21680703
- www-01.ibm.com/support/docview.wss?uid=swg21681933
- www.debian.org/security/2014/dsa-2886
Vendor advisories and official records. Exploit/PoC links are deliberately left out.