dbcve.org
CalciteApplication · Apache

CVE-2022-39135

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-11
Fix available
A fix is available. Upgrade to 1.32.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Apache Calcite 1.22.0 introduced the SQL operators EXISTS_NODE, EXTRACT_XML, XML_TRANSFORM and EXTRACT_VALUE do not restrict XML External Entity references in their configuration, making them vulnerable to a potential XML External Entity (XXE) attack. Therefore any client exposing these operators, typically by using Oracle dialect (the first three) or MySQL dialect (the last one), is affected by this vulnerability (the extent of it will depend on the user under which the application is running). From Apache Calcite 1.32.0 onwards, Document Type Declarations and XML External Entity resolution are disabled on the impacted operators.

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

Apache Calcite versions 1.22.0 through 1.31.0 contain vulnerable XML processing in four SQL operators (EXISTS_NODE, EXTRACT_XML, XML_TRANSFORM for Oracle dialect; EXTRACT_VALUE for MySQL dialect) that fail to disable XML External Entity (XXE) resolution, allowing attackers to inject malicious XML that can read local files or cause denial of service.

MitigationUpgrade Apache Calcite to version 1.32.0 or later where DTD and XXE resolution are disabled by default; if upgrade is not feasible, implement custom XML parser configuration to disable external entities before passing XML to these operators.

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
CalciteApplication
Affected:>= 1.22.0, < 1.32.0

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
High
Integrity
High
Availability
High

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

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 Apache Calcite version in use
    Locate the calcite JAR file or dependency (e.g., calcite-core-x.x.x.jar) and check its version. In Maven projects, run 'mvn dependency:tree | grep calcite' or check pom.xml for the calcite dependency version.
    Affected if The installed version is 1.22.0 through 1.31.0 (inclusive)
  2. Determine if Oracle dialect XML operators are in use
    Search application logs, SQL query logs, or codebase for usage of EXISTS_NODE, EXTRACT_XML, or XML_TRANSFORM functions in Oracle dialect contexts. These appear in SQL queries like SELECT EXISTS_NODE(xml_col, '/path') FROM table.
    Affected if These operators are being executed against untrusted or externally-supplied XML input
  3. Determine if MySQL dialect XML operator is in use
    Search for usage of the EXTRACT_VALUE function in MySQL dialect contexts. Check SQL query logs or application code that submits XML-processing queries to Calcite.
    Affected if EXTRACT_VALUE is being executed against untrusted or externally-supplied XML input
  4. Check if Calcite is exposed to untrusted XML input
    Review whether user-supplied or network-received XML data is passed directly to Calcite's XML operators without prior sanitization or use of a secured parser. Inspect the data flow from input sources to the SQL execution layer.
    Affected if Untrusted XML content can reach the vulnerable operators without external entity resolution being disabled

A user is affected if their Apache Calcite version is between 1.22.0 and 1.31.0 AND they process untrusted XML through the EXISTS_NODE, EXTRACT_XML, XML_TRANSFORM (Oracle) or EXTRACT_VALUE (MySQL) operators.

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 1.32.0 or later
Fixed in 1.32.0
Interim mitigation

Upgrade Apache Calcite to version 1.32.0 or later where DTD and XXE resolution are disabled by default; if upgrade is not feasible, implement custom XML parser configuration to disable external entities before passing XML to these operators.

Recommended fix High confidence

1.32.0 or later

  1. Upgrade Apache Calcite to version 1.32.0 or later to resolve the XXE vulnerability
Caveat DTD and XXE resolution are disabled in 1.32.0+, which may affect legitimate XML processing that depends on DTDs

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

Fix this in Calcite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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