Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2021-23463

XXE (XML External Entity) in com.h2database:h2 (CVE-2021-23463)

Summary

Vulnerability in com.h2database:h2 (CVE-2021-23463). Confidential information can be exposed externally. Mitigation: upgrade to 2.0.202 or later.

Original description

The description as published by the source.

H2 is an embeddable RDBMS written in Java. The package com.h2database:h2 from 1.4.198 and before 2.0.202 are vulnerable to XML External Entity (XXE) Injection via the org.h2.jdbc.JdbcSQLXML class object, when it receives parsed string data from org.h2.jdbc.JdbcResultSet.getSQLXML() method. If it executes the getSource() method when the parameter is DOMSource.class it will trigger the vulnerability.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-2021-23463 has been found in com.h2database:h2.
Confidential information can be exposed externally.
What to do: upgrade com.h2database:h2 to 2.0.202 or later.
If unsure, ask your IT team or search "com.h2database:h2 CVE-2021-23463" on the vendor's site.

CVE-2021-23463 (com.h2database:h2) — CWE-611
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.0.202 — 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 com.h2database:h2.

📍 Affected scope

Check the vendor advisory for the affected versions of com.h2database:h2.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 2.0.202.

🛡️ 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・依存マニフェストで com.h2database:h2 を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade com.h2database:h2 to 2.0.202

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

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

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

Affected packages

Maven com.h2database:h2
[{"type":"ECOSYSTEM","events":[{"introduced":"1.4.198"},{"fixed":"2.0.202"}]}]

References

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