GeoJSON URL validation can expose server files and environment variables to unauthorized users
Only Metabase x.40.0 through x.40.4 with the custom GeoJSON map feature in admin settings is affected. Fixed in 0.40.5 and 1.40.5.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 0.40.5, 1.40.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: active
- Automatable: yes
- Technical impact: total
Summary
Metabase, an open source data analytics platform, is affected through its custom GeoJSON map feature in the admin settings. Attackers could abuse this feature to read server files and environment variables because the URLs it loads were not validated.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Metabase is an open source data analytics platform. In affected versions a security issue has been discovered with the custom GeoJSON map (`admin->settings->maps->custom maps->add a map`) support and potential local file inclusion (including environment variables). URLs were not validated prior to being loaded. This issue is fixed in a new maintenance release (0.40.5 and 1.40.5), and any subsequent release after that. If you’re unable to upgrade immediately, you can mitigate this by including rules in your reverse proxy or load balancer or WAF to provide a validation filter before the application.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- CISA SSVC assessment
Exploitation: active · Automatable: yes · Technical impact: total
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- metabase metabase
fixed in 0.40.5; From 1.0.0 · fixed in 1.40.5
References 2
GitHub · metabase/metabase
Questions about CVE-2021-41277
What does this mean?
The GeoJSON URL validation flaw is a local file inclusion bug. It can let a user read server files and environment variables that should stay private.Source: github.com
Am I affected, and how do I check?
Versions x.40.0 through x.40.4 are affected, but only where the custom GeoJSON map feature in the admin settings is used. Check the installed version number and whether a custom GeoJSON map is configured in the admin settings.Source: github.com
What should I do about it?
Upgrade to 0.40.5 or 1.40.5, or to any later release.Source: github.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-11-12, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data