# CVE-2022-24853: File system exposure in Metabase

> Attackers can exploit a proxy flaw to access local files and perform NTLM relay attacks, potentially stealing system password hashes.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-5cfq-582c-c38m

## What is CVE-2022-24853?

CVE-2022-24853 is a medium-severity server-side request forgery vulnerability in metabase, published on 14 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Metabase is an open source business intelligence and analytics application. Metabase has a proxy to load arbitrary URLs for JSON maps as part of our GeoJSON support. While we do validation to not return contents of arbitrary URLs, there is a case where a particularly crafted request could result in file access on windows, which allows enabling an `NTLM relay attack`, potentially allowing an attacker to receive the system password hash. If you use Windows and are on this version of Metabase, please upgrade immediately. 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-24853?

It affects 1 product.


Products: Metabase Metabase.

## How do I fix CVE-2022-24853?

No fix has been published for CVE-2022-24853 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-24853 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24853 exists.

Public exploit code:

- Metabase NTLM Attack  (github_poc): https://github.com/secure-77/CVE-2022-24853

## Other vulnerabilities in metabase

- [CVE-2026-72898](https://insights.sbomify.com/CVE-2026-72898/): Metabase SQL Injection (critical 10.0, exploited in the wild)
- [CVE-2021-41277](https://insights.sbomify.com/CVE-2021-41277/): Metabase GeoJSON API Local File Inclusion (critical 10.0, exploited in the wild)
- [CVE-2026-50148](https://insights.sbomify.com/CVE-2026-50148/): Metabase: Remote Code Execution via Snowflake JDBC Driver Arbitrary File Write (critical 10.0)
- [CVE-2023-37470](https://insights.sbomify.com/CVE-2023-37470/): Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint (critical 10.0)
- [CVE-2026-59827](https://insights.sbomify.com/CVE-2026-59827/): Metabase: Unsafe Deserialization of H2 Query Results (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24853 and fix it if it is affected.

What it is: CVE-2022-24853 is a medium-severity server-side request forgery vulnerability in metabase, published on 14 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24853 exists.

Affected product: metabase. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24853/ (Markdown: https://insights.sbomify.com/CVE-2022-24853/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24853
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24853
- OSV: https://osv.dev/vulnerability/CVE-2022-24853

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24853/
Summaries are generated and may contain mistakes; the official description above is the record.