Categories
CVE-2022-39135

XXE (XML External Entity) in org.apache.calcite:calcite-core (CVE-2022-39135)

Summary

Vulnerability in org.apache.calcite:calcite-core (CVE-2022-39135). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.32.0 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-39135 has been found in org.apache.calcite:calcite-core.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.apache.calcite:calcite-core to 1.32.0 or later.
If unsure, ask your IT team or search "org.apache.calcite:calcite-core CVE-2022-39135" on the vendor's site.

CVE-2022-39135 (org.apache.calcite:calcite-core) — CWE-611
Patched: 1.32.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-611) exists in org.apache.calcite:calcite-core.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.calcite:calcite-core.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.32.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.calcite:calcite-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.apache.calcite:calcite-core to 1.32.0

    ステージング環境で 1.32.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.apache.calcite:calcite-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.32.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details