CVE-2023-37470
No exploitation reported by the sources we read.
- Published2023-08-04
- Fixed in1.46.6.4 · 1.45.4.3 · 1.44.7.3 · 1.43.7.3 · 0.46.6.4 · 0.45.4.3
- WeaknessCWE-94
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Metabase is an open-source business intelligence and analytics platform. Prior to versions 0.43.7.3, 0.44.7.3, 0.45.4.3, 0.46.6.4, 1.43.7.3, 1.44.7.3, 1.45.4.3, and 1.46.6.4, a vulnerability could potentially allow remote code execution on one's Metabase server. The core issue is that one of the supported data warehouses (an embedded in-memory database H2), exposes a number of ways for a connection string to include code that is then executed by the process running the embedded database. Because Metabase allows users to connect to databases, this means that a user supplied string can be used to inject executable code. Metabase allows users to validate their connection string before adding a database (including on setup), and this validation API was the primary vector used as it can be called without validation. Versions 0.43.7.3, 0.44.7.3, 0.45.4.3, 0.46.6.4, 1.43.7.3, 1.44.7.3, 1.45.4.3, and 1.46.6.4 fix this issue by removing the ability of users to add H2 databases entirely. As a workaround, it is possible to block these vulnerabilities at the network level by blocking the endpoints `POST /api/database`, `PUT /api/database/:id`, and `POST /api/setup/validateuntil`. Those who use H2 as a file-based database should migrate to SQLite.
Timeline
dates in UTC- 2023-08-0416:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-37470?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-37470?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.46 | ≥ 1.46.0, < 1.46.6.4 | 1.46.6.4 | NVD |
| 1.45 | ≥ 1.45.0, < 1.45.4.3 | 1.45.4.3 | NVD |
| 1.44 | ≥ 1.44.0, < 1.44.7.3 | 1.44.7.3 | NVD |
| 1.43 | < 1.43.7.3 | 1.43.7.3 | NVD |
| 0.46 | ≥ 0.46.0, < 0.46.6.4 | 0.46.6.4 | NVD |
| 0.45 | ≥ 0.45.0, < 0.45.4.3 | 0.45.4.3 | NVD |
| 0.44 | ≥ 0.44.0, < 0.44.7.3 | 0.44.7.3 | NVD |
| 0.43 | < 0.43.7.3 | 0.43.7.3 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Metabase to 1.46.6.4 · 1.45.4.3 · 1.44.7.3 · 1.43.7.3 · 0.46.6.4 · 0.45.4.3 · 0.44.7.3 · 0.43.7.3
Advisories and patches
- github.comMitigation · Patch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2023-08-04
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2023-37470?
Is CVE-2023-37470 actively exploited?
What is the CVSS score for CVE-2023-37470?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.