# CVE-2014-0107: Improper Authorization in Apache Xalan-Java > Remote attackers can bypass security restrictions in Apache Xalan-Java to load arbitrary classes or access external resources via crafted XSLT properties. - **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Apr 2014 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2014-0107, DSA-2886-1, GHSA-rc2w-r4jq-7pfx, MGASA-2014-0152, RHSA-2014:0348, RHSA-2014:0453, RHSA-2014:0591, openSUSE-SU-2024:10404-1 ## What is CVE-2014-0107? CVE-2014-0107 is a high-severity vulnerability in Oracle Webcenter Sites, published on 15 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-264 ## Which versions are affected by CVE-2014-0107? 2 open source packages ship an affected version, including xalan:xalan. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `xalan:xalan` | Maven | All versions | 2.7.2 | | `xalan:xalan` | Maven | All versions | 2.7.2 | | `xalan-j2` | Red Hat:enterprise_linux:5::client | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-manual` | Red Hat:enterprise_linux:5::client | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-xsltc` | Red Hat:enterprise_linux:5::client | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-demo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-javadoc` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2` | Red Hat:enterprise_linux:5::server | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-demo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-javadoc` | Red Hat:enterprise_linux:5::server | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-manual` | Red Hat:enterprise_linux:5::server | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2-xsltc` | Red Hat:enterprise_linux:5::server | All versions | 0:2.7.0-6jpp.2 | | `xalan-j2` | Red Hat:enterprise_linux:6::client | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-demo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-javadoc` | Red Hat:enterprise_linux:6::client | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-manual` | Red Hat:enterprise_linux:6::client | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-xsltc` | Red Hat:enterprise_linux:6::client | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-demo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-javadoc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-manual` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-xsltc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2` | Red Hat:enterprise_linux:6::server | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-demo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-javadoc` | Red Hat:enterprise_linux:6::server | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-manual` | Red Hat:enterprise_linux:6::server | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-xsltc` | Red Hat:enterprise_linux:6::server | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-demo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-javadoc` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-manual` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2-xsltc` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.7.0-9.9.el6_5 | | `xalan-j2` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:2.7.1-12_patch_08.ep5.el4 | | `xalan-j2` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:2.7.1-12_patch_08.ep5.el5 | | `xalan-j2` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:2.7.1-12_patch_08.ep5.el6 | | `xalan-j2-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:2.7.1-9.redhat_7.1.ep6.el5 | Products: Apache Xalan-Java, Oracle Webcenter Sites. ## How do I fix CVE-2014-0107? Upgrade xalan:xalan to 2.7.2 or later. ## Is CVE-2014-0107 being exploited? There is no known exploitation of CVE-2014-0107 in the wild and no public exploit code. ## Other vulnerabilities in Oracle Webcenter Sites - [CVE-2022-34169](https://insights.sbomify.com/CVE-2022-34169/): Apache Xalan Java XSLT library is vulnerable to an integer truncation issue when processing malicious XSLT stylesheets (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2014-0107 and fix it if it is affected. What it is: CVE-2014-0107 is a high-severity vulnerability in Oracle Webcenter Sites, published on 15 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2014-0107 in the wild and no public exploit code. Affected packages and fixed versions: - xalan:xalan (Maven): affected all versions; fixed in 2.7.2 - xalan:xalan (Maven): affected all versions; fixed in 2.7.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2014-0107/ (Markdown: https://insights.sbomify.com/CVE-2014-0107/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0107 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0107 - OSV: https://osv.dev/vulnerability/CVE-2014-0107 --- From sbomify Insights: https://insights.sbomify.com/CVE-2014-0107/ Summaries are generated and may contain mistakes; the official description above is the record.