CVE-2022-39361
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 · uneditedMetabase is data visualization software. Prior to versions 0.44.5, 1.44.5, 0.43.7, 1.43.7, 0.42.6, 1.42.6, 0.41.9, and 1.41.9, H2 (Sample Database) could allow Remote Code Execution (RCE), which can be abused by users able to write SQL queries on H2 databases. This issue is patched in versions 0.44.5, 1.44.5, 0.43.7, 1.43.7, 0.42.6, 1.42.6, 0.41.9, and 1.41.9. Metabase no longer allows DDL statements in H2 native queries.
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 confidenceMetabase versions prior to 0.44.5/1.44.5 (and other patched versions listed) contain an RCE vulnerability in the H2 Sample Database where users with SQL query privileges can execute arbitrary code by abusing DDL statements in H2 native queries.
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>= 0.41.0, < 0.41.9>= 0.42.0, < 0.42.6>= 0.43.0, < 0.43.7>= 0.44.0, < 0.44.5>= 1.41.0, < 1.41.9>= 1.42.0, < 1.42.6>= 1.43.0, < 1.43.7>= 1.44.0, < 1.44.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Metabase versionCheck the Metabase admin panel under 'About Metabase' or query the API endpoint /api/health to retrieve the current version numberAffected if The installed version falls within any of these ranges: >= 0.41.0 and < 0.41.9; >= 0.42.0 and < 0.42.6; >= 0.43.0 and < 0.43.7; >= 0.44.0 and < 0.44.5; >= 1.41.0 and < 1.41.9; >= 1.42.0 and < 1.42.6; >= 1.43.0 and < 1.43.7; >= 1.44.0 and < 1.44.5
-
Confirm H2 Sample Database is in useNavigate to Admin > Databases and inspect the configured databases. Identify if the 'Sample Database' is present and its engine type is H2Affected if The H2 Sample Database is configured and available as a data source
-
Verify SQL query execution permissionsNavigate to Admin > Permissions and review which users or groups have 'Native queries' or 'Write' permissions granted on the H2 Sample DatabaseAffected if Any user or group has permissions to write or execute native SQL queries against the H2 Sample Database
You are affected if your Metabase version is within the affected ranges AND the H2 Sample Database is enabled AND users have SQL native query privileges on that database.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.41.90.42.60.43.7
Upgrade Metabase to one of the patched versions (0.44.5, 1.44.5, 0.43.7, 1.43.7, 0.42.6, 1.42.6, 0.41.9, or 1.41.9) which disable DDL statements in H2 native queries.
Minimum: upgrade to 0.41.9/1.41.9 (for 0.41.x), 0.42.6/1.42.6 (for 0.42.x), 0.43.7/1.43.7 (for 0.43.x), or 0.44.5/1.44.5 (for 0.44.x) - choose the latest in your release line
- Identify your current Metabase version from the admin settings or startup logs
- Backup your Metabase application database before upgrading
- Download the fixed version for your release line: 0.41.9 or 1.41.9 (for 0.41.x), 0.42.6 or 1.42.6 (for 0.42.x), 0.43.7 or 1.43.7 (for 0.43.x), 0.44.5 or 1.44.5 (for 0.44.x)
- Stop the running Metabase instance
- Replace the Metabase JAR file with the new version
- Start Metabase with the same application database to trigger automatic migration
- Verify the upgrade by checking the version in Admin > Settings > General
- Confirm that H2 native queries now block DDL statements as the patch specifies
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-39361 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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