Sensitive data disclosure via redirect-based SSRF
Published Oct 26, 2022 · Updated May 7, 2025
SSRF in Metabase before 44.5 allows remote authenticated users to read internal resources through the /api/geojson url parameter. The endpoint checks the initial URL against a blacklist but follows attacker-controlled HTTP 301 or 302 redirects to blocked link-local hosts. A valid Metabase session is required, and exploitation can disclose responses from internal services or cloud metadata endpoints without modifying them.
Summary
What happened
SSRF in Metabase before 44.5 allows remote authenticated users to read internal resources through the /api/geojson url parameter. The endpoint checks the initial URL against a blacklist but follows attacker-controlled HTTP 301 or 302 redirects to blocked link-local hosts. A valid Metabase session is required, and exploitation can disclose responses from internal services or cloud metadata endpoints without modifying them.
The record
- CVE
- CVE-2022-43776
- Published
- Oct 26, 2022
- Updated
- May 7, 2025
- Vendor
- Metabase
- Product
- Metabase
- Classifications
- CWE-918, T1552.005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 26, 2022CVE publishedPublication date reported by the CVE source.
- May 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<44.5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Redirect-based GeoJSON SSRF proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo