CVE-2022-43776 Server-side request forgery in Metabase
Attackers can exploit the url parameter in the geojson endpoint to perform Server Side Request Forgery, bypassing previous blacklist protections via redirects.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-43776?
CVE-2022-43776 is a medium-severity server-side request forgery vulnerability in Metabase, published on 26 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The url parameter of the /api/geojson endpoint in Metabase versions <44.5 can be used to perform Server Side Request Forgery attacks. Previously implemented blacklists could be circumvented by leveraging 301 and 302 redirects.
Weakness: CWE-918
Which versions are affected by CVE-2022-43776?
It affects 1 product.
Products include Metabase Metabase.
How do I fix CVE-2022-43776?
No fix has been published for CVE-2022-43776 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2022-43776 being exploited?
There is no known exploitation of CVE-2022-43776 in the wild and no public exploit code.
Other vulnerabilities in Metabase
- CVE-2026-72898 Metabase SQL Injection
- CVE-2021-41277 Metabase GeoJSON API Local File Inclusion
- CVE-2026-50148 Metabase: Remote Code Execution via Snowflake JDBC Driver Arbitrary File Write
- CVE-2023-37470 Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint
- CVE-2026-59827 Metabase: Unsafe Deserialization of H2 Query Results
Sources
Also known as GHSA-mppc-g8x5-rq8c.