Skip to content

Apache Calcite before 1.32.0 vulnerable to potential XML External Entity (XXE) attack

Critical severity GitHub Reviewed Published Sep 12, 2022 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven org.apache.calcite:calcite-core (Maven)

Affected versions

< 1.32.0

Patched versions

1.32.0

Description

In Apache Calcite prior to version 1.32.0 the SQL operators EXISTS_NODE, EXTRACT_XML, XML_TRANSFORM and EXTRACT_VALUE do not restrict XML External Entity references in their configuration, which makes 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.

References

Published by the National Vulnerability Database Sep 11, 2022
Published to the GitHub Advisory Database Sep 12, 2022
Reviewed Sep 15, 2022
Last updated Feb 1, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.199%
(59th percentile)

Weaknesses

CVE ID

CVE-2022-39135

GHSA ID

GHSA-fj2m-w3wv-x9pr

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.