Skip to content

← Public intelligence

Maven package

xalan:xalan

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5MavenPublished

    Apache Xalan Java XSLT library integer truncation issue when processing malicious XSLT stylesheets

    CVE-2022-34169 · GHSA-9339-86wc-4qgf

    Affected
    • Maven xalan:xalan < 2.7.3
    Fixed in
    2.7.3· Vendor fix available
    Issue
    The Apache Xalan Java XSLT library is vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. This can be used to corrupt Java class files generated by the internal XSLTC compiler and execute arbitrary Java bytecode. A fix for this issue was published in September 2022 as part of an anticipated 2.7.3 release.

    Recommended action: Upgrade to 2.7.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. UnratedMavenPublished

    Improper Authorization in Apache Xalan-Java

    CVE-2014-0107 · GHSA-rc2w-r4jq-7pfx

    Affected
    • Maven xalan:xalan < 2.7.2
    Fixed in
    2.7.2· Vendor fix available
    Issue
    The TransformerFactory in Apache Xalan-Java before 2.7.2 does not properly restrict access to certain properties when FEATURESECUREPROCESSING 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.

    Recommended action: Upgrade to 2.7.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →