dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-21282

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 15.0.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JAXP). Supported versions that are affected are Oracle Java SE: 7u321, 8u311, 11.0.13, 17.0.1; Oracle GraalVM Enterprise Edition: 20.3.4 and 21.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability can also be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).

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 · high confidence

This is an XML external entity (XXE) vulnerability in the JAXP (Java API for XML Processing) component of Oracle Java SE and GraalVM Enterprise Edition. The flaw allows an unauthenticated remote attacker to exploit XML parsing to gain unauthorized read access to a subset of accessible data, primarily impacting applications that process untrusted XML content.

MitigationApply the relevant Oracle security patch to upgrade to a patched Java version (beyond 7u321, 8u311, 11.0.13, 17.0.1) or apply workarounds such as disabling external entity processing in XML parsers and ensuring sandboxed environments are properly configured.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Debian LinuxOperating system
Affected:= 9.0= 10.0= 11.0
OpenjdkApplication
Affected:>= 11, <= 11.0.13>= 13, <= 13.0.9>= 15, <= 15.0.5= 7= 8= 17= 17.0.1
GraalvmApplication
Affected:= 20.3.4= 21.3.0
JdkApplication
Affected:= 1.7.0= 1.8.0= 11.0.13= 17.0.1
JreApplication
Affected:= 1.7.0= 1.8.0= 11.0.13= 17.0.1
7 Mode Transition ToolApplication
Affected:all versions
Active Iq Unified ManagerApplication
Affected:all versions
Cloud Insights Acquisition UnitApplication
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
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Java version
    Run 'java -version' or 'java -fullversion' from the command line to see the installed Java runtime version
    Affected if The version matches any of the affected ranges: JDK/JRE 7, 8, 11.0.13, 17.0.1; OpenJDK 11.0.13 or below, 13.0.9 or below, 15.0.5 or below, or versions 17/17.0.1; GraalVM 20.3.4 or 21.3.0
  2. Check for Java in Debian packages
    Run 'dpkg -l | grep -i openjdk' or 'apt list --installed | grep -i jdk' to list installed Java packages on Debian systems
    Affected if Package version corresponds to Debian 9.0, 10.0, or 11.0 and contains affected Java versions
  3. Determine if application uses JAXP XML parsing
    Inspect application code or configuration for usage of Java XML parsing APIs such as DocumentBuilder, SAXParser, or XMLStreamReader from javax.xml.parsers or javax.xml.stream packages
    Affected if The application or service uses JAXP-based XML parsers to process XML documents
  4. Assess if XML input is untrusted
    Review whether the Java application processes XML from external or untrusted sources such as user uploads, API requests, remote services, or files outside the trusted codebase
    Affected if The application processes XML content from untrusted or external sources without disabling external entity processing
  5. Check NetApp product versions
    For NetApp products (7 Mode Transition Tool, Active IQ Unified Manager, Cloud Insights Acquisition Unit), check the installed product version via its admin interface or command line
    Affected if Any version of these NetApp products is installed (all versions are affected according to the advisory)

You are affected if you run any of the listed Java versions AND your application uses JAXP to parse XML from untrusted sources, or if you run any version of the affected NetApp products.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 15.0.5
Interim mitigation

Apply the relevant Oracle security patch to upgrade to a patched Java version (beyond 7u321, 8u311, 11.0.13, 17.0.1) or apply workarounds such as disabling external entity processing in XML parsers and ensuring sandboxed environments are properly configured.

Recommended fix Moderate confidence

Oracle Java SE 7u331+/8u321+/11.0.14+/17.0.2+ or Oracle GraalVM Enterprise Edition 20.3.5+/21.3.1+

  1. Identify the exact Java/JDK/JRE version installed using 'java -version' or checking the package manager
  2. For Oracle Java SE: upgrade to Oracle Java SE 7u331/8u321/11.0.14/17.0.2 or later (or the latest available CPU patch)
  3. For Oracle GraalVM Enterprise Edition: upgrade to GraalVM Enterprise Edition 20.3.5/21.3.1 or later
  4. For OpenJDK distributions: upgrade to OpenJDK 11.0.14+, 13.0.10+, 15.0.6+, or a version beyond the listed affected releases
  5. For Debian systems: run 'apt-get update && apt-get upgrade' or 'apt-get dist-upgrade' to apply security updates for openjdk packages
  6. Verify the upgrade was successful by running 'java -version' and confirming the new version number
  7. If using Java Web Start or applets, ensure the sandboxed deployment is updated as well
Caveat Minor point release updates typically have low risk; major version upgrades (e.g., 11 to 17) may require code compatibility testing

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21282 — 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-21282 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