gsd-2023-37470
Vulnerability from gsd
Modified
2023-12-13 01:20
Details
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.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2023-37470", "id": "GSD-2023-37470" }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2023-37470" ], "details": "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\u0027s 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.", "id": "GSD-2023-37470", "modified": "2023-12-13T01:20:24.451882Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2023-37470", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "metabase", "version": { "version_data": [ { "version_affected": "=", "version_value": "\u003c 0.43.7.3" }, { "version_affected": "=", "version_value": "\u003e= 0.44.0.0, \u003c 0.44.7.3" }, { "version_affected": "=", "version_value": "\u003e= 0.45.0.0, \u003c 0.45.4.3" }, { "version_affected": "=", "version_value": "\u003e= 0.46.0.0, \u003c 0.46.6.4" }, { "version_affected": "=", "version_value": "\u003e= 1.0.0, \u003c 1.43.7.3" }, { "version_affected": "=", "version_value": "\u003e= 1.44.0.0, \u003c 1.44.7.3" }, { "version_affected": "=", "version_value": "\u003e= 1.45.0.0, \u003c 1.45.4.3" }, { "version_affected": "=", "version_value": "\u003e= 1.46.0.0, \u003c 1.46.6.4" } ] } } ] }, "vendor_name": "metabase" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "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\u0027s 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." } ] }, "impact": { "cvss": [ { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 10, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "CHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H", "version": "3.1" } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "cweId": "CWE-94", "lang": "eng", "value": "CWE-94: Improper Control of Generation of Code (\u0027Code Injection\u0027)" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83", "refsource": "MISC", "url": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83" } ] }, "source": { "advisory": "GHSA-p7w3-9m58-rq83", "discovery": "UNKNOWN" } }, "nvd.nist.gov": { "configurations": { "CVE_data_version": "4.0", "nodes": [ { "children": [], "cpe_match": [ { "cpe23Uri": "cpe:2.3:a:metabase:metabase:*:*:*:*:enterprise:*:*:*", "cpe_name": [], "versionEndExcluding": "1.46.6.4", "versionStartIncluding": "1.46.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:metabase:metabase:*:*:*:*:enterprise:*:*:*", "cpe_name": [], "versionEndExcluding": "1.45.4.3", "versionStartIncluding": "1.45.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:metabase:metabase:*:*:*:*:enterprise:*:*:*", "cpe_name": [], "versionEndExcluding": "1.44.7.3", "versionStartIncluding": "1.44.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:metabase:metabase:*:*:*:*:-:*:*:*", "cpe_name": [], "versionEndExcluding": "0.46.6.4", "versionStartIncluding": "0.46.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:metabase:metabase:*:*:*:*:-:*:*:*", "cpe_name": [], "versionEndExcluding": "0.45.4.3", "versionStartIncluding": "0.45.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:metabase:metabase:*:*:*:*:-:*:*:*", "cpe_name": [], "versionEndExcluding": "0.44.7.3", "versionStartIncluding": "0.44.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:metabase:metabase:*:*:*:*:-:*:*:*", "cpe_name": [], "versionEndExcluding": "0.43.7.3", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:metabase:metabase:*:*:*:*:enterprise:*:*:*", "cpe_name": [], "versionEndExcluding": "1.43.7.3", "vulnerable": true } ], "operator": "OR" } ] }, "cve": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2023-37470" }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "en", "value": "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\u0027s 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." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "en", "value": "CWE-94" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83", "refsource": "MISC", "tags": [ "Mitigation", "Patch", "Third Party Advisory" ], "url": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83" } ] } }, "impact": { "baseMetricV3": { "cvssV3": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 9.8, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.1" }, "exploitabilityScore": 3.9, "impactScore": 5.9 } }, "lastModifiedDate": "2023-08-09T20:57Z", "publishedDate": "2023-08-04T16:15Z" } } }
Loading...
Loading...
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.