dbcve.org
Xalan JavaApplication · Apache

CVE-2022-34169

HIGH · 7.5 CVSS v3.1 Published 2022-07-19
Fix available
A fix is available. Upgrade to after 17.0.3 or later.
See remediation →
84/100
Remediation priority · High
High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. Users are recommended to update to version 2.7.3 or later. Note: Java runtimes (such as OpenJDK) include repackaged copies of Xalan.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Xalan JavaApplication
Affected:<= 2.7.2
Debian LinuxOperating system
Affected:= 10.0= 11.0
OpenjdkApplication
Affected:>= 11, <= 11.0.15>= 13, <= 13.0.11>= 15, <= 15.0.7>= 17, <= 17.0.3= 7= 8= 18
FedoraOperating system
Affected:= 35= 36
GraalvmApplication
Affected:= 20.3.6= 21.3.2= 22.1.0
JdkApplication
Affected:= 1.7.0= 1.8.0= 11.0.15.1= 17.0.3.1= 18.0.1.1
JreApplication
Affected:= 1.7.0= 1.8.0= 11.0.15.1= 17.0.3.1= 18.0.1.1
7 Mode Transition ToolApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 17.0.3
Vendor patch www.openwall.com →
Recommended fix High confidence

Xalan Java 2.7.3+ | OpenJDK 11.0.16+ | OpenJDK 17.0.4+

  1. Identify the specific Xalan Java or Java runtime (OpenJDK/JDK/JRE) version in use
  2. For direct Xalan Java usage: upgrade Xalan Java to version 2.7.3 or later
  3. For Java runtime bundled Xalan: upgrade the JDK/JRE to a version that includes fixed Xalan. For OpenJDK 11, use 11.0.16 or later; for OpenJDK 17, use 17.0.4 or later; for JDK/JRE 11, use 11.0.16 or later; for JDK/JRE 17, use 17.0.4 or later
  4. After upgrade, verify the Xalan version in the runtime matches 2.7.3 or later using: java -cp /path/to/xalan.jar org.apache.xalan.Version
Caveat Upgrading Java runtime may introduce behavioral changes in other Java components; regression testing recommended

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34169 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34169 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data