dbcve.org
MetabaseApplication

CVE-2022-24854

HIGH · 8.8 CVSS v3.1 Published 2022-04-14
Fix available
A fix is available. Upgrade to 0.41.7 / 0.42.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Metabase is an open source business intelligence and analytics application. SQLite has an FDW-like feature called `ATTACH DATABASE`, which allows connecting multiple SQLite databases via the initial connection. If the attacker has SQL permissions to at least one SQLite database, then it can attach this database to a second database, and then it can query across all the tables. To be able to do that the attacker also needs to know the file path to the second database. Users are advised to upgrade as soon as possible. If you're unable to upgrade, you can modify your SQLIte connection strings to contain the url argument `?limit_attached=0`, which will disallow making connections to other SQLite databases. Only users making use of SQLite are affected.

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 confidence

Metabase's SQLite integration allows the ATTACH DATABASE feature, which permits connecting multiple SQLite databases through the initial connection. An attacker with SQL permissions to any SQLite database can attach additional SQLite databases (if they know the file path) and query across all tables, enabling unauthorized data access to otherwise inaccessible databases.

MitigationUpgrade to the patched Metabase version, or modify SQLite connection strings to include the url parameter '?limit_attached=0' to prevent attachment of additional databases.

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
MetabaseApplication
Affected:>= 0.41.0, < 0.41.7>= 0.42.0, < 0.42.4>= 1.41.0, < 1.41.7>= 1.42.0, < 1.42.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Metabase installation and version
    Check the Metabase admin panel under 'About Metabase' or inspect the JAR filename/application logs to determine the installed version number
    Affected if The installed version falls within >= 0.41.0 and < 0.41.7, >= 0.42.0 and < 0.42.4, >= 1.41.0 and < 1.41.7, or >= 1.42.0 and < 1.42.4
  2. Confirm SQLite database drivers are in use
    Navigate to Metabase admin panel, go to 'Databases', and review the list of configured database connections to identify any SQLite databases
    Affected if At least one SQLite database connection exists in the Metabase instance
  3. Verify SQLite connection configuration
    Inspect the SQLite database connection settings in Metabase admin panel, specifically examining the connection string or JDBC URL configuration
    Affected if The SQLite connection URL does not contain the 'limit_attached=0' parameter, meaning the ATTACH DATABASE feature remains enabled
  4. Check for unauthorized database access risk
    Review the SQL query logs or audit logs if available, looking for any ATTACH DATABASE statements executed against SQLite connections
    Affected if ATTACH DATABASE queries have been executed against SQLite databases in the environment

A user is affected if they run a vulnerable Metabase version (as specified in the affected ranges) with at least one SQLite database connection that lacks the limit_attached=0 mitigation in its connection configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.41.7 / 0.42.4 / 1.41.7 or later
Fixed in 0.41.70.42.41.41.7
Interim mitigation

Upgrade to the patched Metabase version, or modify SQLite connection strings to include the url parameter '?limit_attached=0' to prevent attachment of additional databases.

Recommended fix High confidence

Metabase 0.41.7, 0.42.4, 1.41.7, or 1.42.4 (depending on your current major version)

  1. Identify Metabase instances using SQLite as the database backend
  2. Upgrade Metabase to the fixed version corresponding to your current branch: for 0.41.x upgrade to 0.41.7, for 0.42.x upgrade to 0.42.4, for 1.41.x upgrade to 1.41.7, for 1.42.x upgrade to 1.42.4
  3. After upgrade, verify that SQLite connections work as expected
  4. Alternatively, if immediate upgrade is not possible, modify SQLite connection strings to include the url argument ?limit_attached=0 to prevent attaching other databases
  5. Test the connection after applying the mitigation parameter
Caveat No breaking changes documented for these minor version upgrades; standard upgrade procedure applies

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Metabase Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24854 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24854 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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