CVE-2022-24855
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 an open source business intelligence and analytics application. In affected versions Metabase ships with an internal development endpoint `/_internal` that can allow for cross site scripting (XSS) attacks, potentially leading to phishing attempts with malicious links that could lead to account takeover. Users are advised to either upgrade immediately, or block access in your firewall to `/_internal` endpoints for Metabase. The following patches (or greater versions) are available: 0.42.4 and 1.42.4, 0.41.7 and 1.41.7, 0.40.8 and 1.40.8.
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 contains an exposed internal development endpoint at /_internal that is vulnerable to cross-site scripting (XSS). Attackers can craft malicious links that execute arbitrary JavaScript in victims' browsers, enabling phishing attacks and potential account takeover.
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.40.0, < 0.40.8>= 0.41.0, < 0.41.7>= 0.42.0, < 0.42.4>= 1.40.0, < 1.40.8>= 1.41.0, < 1.41.7>= 1.42.0, < 1.42.4CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 Metabase versionCheck the Metabase admin panel (Settings > About) or look for the version in the application startup logsAffected if Installed version falls within: 0.40.0-0.40.7, 0.41.0-0.41.6, 0.42.0-0.42.3, 1.40.0-1.40.7, 1.41.0-1.41.6, or 1.42.0-1.42.3
-
Confirm /_internal endpoint is accessibleSend an HTTP GET request to your Metabase host at the path /_internal (for example: curl -I https://your-metabase-host/_internal)Affected if The endpoint returns an HTTP 200 or any response rather than a 404 or connection refused error, indicating it is reachable
-
Verify external exposure of /_internalAccess the /_internal endpoint from outside your internal network, or review firewall/proxy configuration to confirm whether the endpoint is exposed to untrusted networksAffected if The /_internal endpoint is reachable from the public internet or untrusted networks (this is an internal development endpoint that should not be externally accessible)
You are affected if your installed Metabase version is within the affected ranges AND the /_internal development endpoint is accessible (especially externally), as this enables attackers to craft malicious links executing arbitrary JavaScript in user browsers.
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.40.80.41.70.42.4
Block external access to /_internal endpoints at the firewall/proxy level, or upgrade to patched versions 0.42.4+/1.42.4+, 0.41.7+/1.41.7+, or 0.40.8+/1.40.8+.
Upgrade to 0.40.8+, 0.41.7+, 0.42.4+, or 1.40.8+ (or corresponding 1.x versions) depending on your current branch
- Identify your current Metabase version by checking the admin panel or the startup logs
- Determine which version branch you're on (0.40.x, 0.41.x, 0.42.x, or 1.40.x)
- Back up your Metabase database before upgrading
- Download the appropriate fixed version for your branch: 0.40.8+ (or 1.40.8+), 0.41.7+ (or 1.41.7+), or 0.42.4+ (or 1.42.4+)
- Stop the Metabase application
- Replace the Metabase JAR file with the new version
- Start Metabase and verify the application runs correctly
- Verify the /_internal endpoint is no longer accessible or no longer vulnerable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24855 — 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-24855 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