Skip to main content

CVE-2021-41277

Metabase — Metabase GeoJSON API Local File Inclusion Vulnerability

Metabase · CWE-200 — Exposure of sensitive information | CWE-22 — Path traversal · in CISA KEV since 2024-11-12

KEV since 2024 · listed over a yearCISA KEVActively Exploited
84

EVRS 84 of 100 Urgent

Patch This Cycle

Rank 475 of 2,960 tracked

Download PDF

Why it scores 84

Evidence available: 6 of 7 signals

Listed in the CISA KEV catalog, and an EPSS probability of 0.972.

  • CISA KEVApplied
  • RansomwareDid not apply
  • Vendor exploitationDid not apply
  • EPSSApplied
  • Microsoft Exploitability IndexNot applicable
  • Pre-patch disclosureNo data
  • KEV recencyDid not apply
  • CVSSApplied

The band answers “how soon”, not “how bad”. No data for: Pre-patch disclosure. Why some signals show no data

Fix

No fixed version identified yet

CISA required action

Affected versions

  • metabase0.40.00.40.10.40.20.40.30.40.41.40.01.40.11.40.21.40.31.40.4

Remediation

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Evidence

Each value with its source
MeasureValueSource
CVSS base scoreHow severe the flaw is in itself. It does not say how likely an attack is. 7.5 NVD
FIRST EPSSFIRST's estimate of the chance this is exploited in the next 30 days, and how that ranks against all CVEs. 0.972 (99.9th pctl) FIRST EPSS
Actively exploitedWhether a source of record has confirmed attacks using it in the wild. Confirmed CISA KEV
Ransomware campaign useWhether CISA has seen ransomware operators use it. Unknown or none CISA KEV
CISA remediation deadlineThe date US federal agencies must have fixed or mitigated it. 2024-12-03 · KEV since 2024 · listed over a year CISA KEV
Public exploit moduleA module existing is not the same as active exploitation. None known Metasploit
EUVD cross-referenceENISA's record: CVSS 10.0 (v3.1), assigned by GitHub_M. Listed ENISA EUVD

Description

NVD

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.

What CISA says to do