CVE-2023-37470 (GCVE-0-2023-37470)

Vulnerability from cvelistv5 – Published: 2023-08-04 15:12 – Updated: 2024-10-17 14:54
VLAI
Title
Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint
Summary
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.
Severity
10 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
SSVC
Exploitation: none Automatable: yes Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2024-10-17 14:54 UTC
CWE
  • CWE-94 - Improper Control of Generation of Code ('Code Injection')
Assigner
GitHub_M CNA under the mitre root
CNA scorecard C 72/100 over 7861 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
metabase metabase Affected: < 0.43.7.3
Affected: >= 0.44.0.0, < 0.44.7.3
Affected: >= 0.45.0.0, < 0.45.4.3
Affected: >= 0.46.0.0, < 0.46.6.4
Affected: >= 1.0.0, < 1.43.7.3
Affected: >= 1.44.0.0, < 1.44.7.3
Affected: >= 1.45.0.0, < 1.45.4.3
Affected: >= 1.46.0.0, < 1.46.6.4
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T17:16:30.142Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "name": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83",
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2023-37470",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-10-17T14:54:25.239902Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-10-17T14:54:36.299Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "metabase",
          "vendor": "metabase",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 0.43.7.3"
            },
            {
              "status": "affected",
              "version": "\u003e= 0.44.0.0, \u003c 0.44.7.3"
            },
            {
              "status": "affected",
              "version": "\u003e= 0.45.0.0, \u003c 0.45.4.3"
            },
            {
              "status": "affected",
              "version": "\u003e= 0.46.0.0, \u003c 0.46.6.4"
            },
            {
              "status": "affected",
              "version": "\u003e= 1.0.0, \u003c 1.43.7.3"
            },
            {
              "status": "affected",
              "version": "\u003e= 1.44.0.0, \u003c 1.44.7.3"
            },
            {
              "status": "affected",
              "version": "\u003e= 1.45.0.0, \u003c 1.45.4.3"
            },
            {
              "status": "affected",
              "version": "\u003e= 1.46.0.0, \u003c 1.46.6.4"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "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."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "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"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-94",
              "description": "CWE-94: Improper Control of Generation of Code (\u0027Code Injection\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2023-08-04T15:12:43.188Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83"
        }
      ],
      "source": {
        "advisory": "GHSA-p7w3-9m58-rq83",
        "discovery": "UNKNOWN"
      },
      "title": "Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint "
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2023-37470",
    "datePublished": "2023-08-04T15:12:43.188Z",
    "dateReserved": "2023-07-06T13:01:36.998Z",
    "dateUpdated": "2024-10-17T14:54:36.299Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2023-37470",
      "date": "2026-11-13",
      "epss": "0.01349",
      "percentile": "0.71921"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "product": "metabase",
                "vendor": "metabase",
                "versions": [
                  {
                    "status": "affected",
                    "version": "\u003c 0.43.7.3"
                  },
                  {
                    "status": "affected",
                    "version": "\u003e= 0.44.0.0, \u003c 0.44.7.3"
                  },
                  {
                    "status": "affected",
                    "version": "\u003e= 0.45.0.0, \u003c 0.45.4.3"
                  },
                  {
                    "status": "affected",
                    "version": "\u003e= 0.46.0.0, \u003c 0.46.6.4"
                  },
                  {
                    "status": "affected",
                    "version": "\u003e= 1.0.0, \u003c 1.43.7.3"
                  },
                  {
                    "status": "affected",
                    "version": "\u003e= 1.44.0.0, \u003c 1.44.7.3"
                  },
                  {
                    "status": "affected",
                    "version": "\u003e= 1.45.0.0, \u003c 1.45.4.3"
                  },
                  {
                    "status": "affected",
                    "version": "\u003e= 1.46.0.0, \u003c 1.46.6.4"
                  }
                ]
              }
            ],
            "source": "security-advisories@github.com"
          }
        ],
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:a:metabase:metabase:*:*:*:*:-:*:*:*",
                    "matchCriteriaId": "AFE116C8-B5B5-48CE-873D-1E508D1A656A",
                    "versionEndExcluding": "0.43.7.3",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:metabase:metabase:*:*:*:*:enterprise:*:*:*",
                    "matchCriteriaId": "97C698D2-6F8A-4BD4-BC29-80086F1F87C0",
                    "versionEndExcluding": "1.43.7.3",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:metabase:metabase:*:*:*:*:-:*:*:*",
                    "matchCriteriaId": "36C340AD-358E-478B-B75C-4A0A8F52F6C6",
                    "versionEndExcluding": "0.44.7.3",
                    "versionStartIncluding": "0.44.0",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:metabase:metabase:*:*:*:*:-:*:*:*",
                    "matchCriteriaId": "A23C9D19-21F7-4529-8CF7-C20DACA524F3",
                    "versionEndExcluding": "0.45.4.3",
                    "versionStartIncluding": "0.45.0",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:metabase:metabase:*:*:*:*:-:*:*:*",
                    "matchCriteriaId": "87EA14BE-A683-44D4-904D-3DEB8A672958",
                    "versionEndExcluding": "0.46.6.4",
                    "versionStartIncluding": "0.46.0",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:metabase:metabase:*:*:*:*:enterprise:*:*:*",
                    "matchCriteriaId": "A4F52A25-3933-4D5D-A69F-073D31C079D2",
                    "versionEndExcluding": "1.44.7.3",
                    "versionStartIncluding": "1.44.0",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:metabase:metabase:*:*:*:*:enterprise:*:*:*",
                    "matchCriteriaId": "0ECC070D-27E2-40A2-A0D4-E818CBAB857D",
                    "versionEndExcluding": "1.45.4.3",
                    "versionStartIncluding": "1.45.0",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:metabase:metabase:*:*:*:*:enterprise:*:*:*",
                    "matchCriteriaId": "E025C478-8650-4B5E-B92F-9ACD2AA4C8C2",
                    "versionEndExcluding": "1.46.6.4",
                    "versionStartIncluding": "1.46.0",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "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."
          },
          {
            "lang": "es",
            "value": "Metabase es una plataforma de an\u00e1lisis e inteligencia empresarial de c\u00f3digo abierto. Antes de las versiones 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 y 1.46.6.4, una vulnerabilidad pod\u00eda permitir la ejecuci\u00f3n remota de c\u00f3digo en el servidor Metabase. El problema central es que uno de los almacenes de datos soportados (una base de datos en memoria embebida H2), expone un varias maneras para que una cadena de conexi\u00f3n incluya c\u00f3digo que luego es ejecutado por el proceso que ejecuta la base de datos embebida. Debido a que Metabase permite a los usuarios conectarse a bases de datos, esto significa que una cadena suministrada por el usuario puede ser utilizada para inyectar c\u00f3digo ejecutable. Metabase permite a los usuarios validar su cadena de conexi\u00f3n antes de a\u00f1adir una base de datos (incluso en la configuraci\u00f3n), y esta API de validaci\u00f3n fue el principal vector utilizado, ya que puede ser llamada sin validaci\u00f3n. Las versiones 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 y 1.46.6.4 solucionan este problema eliminando por completo la posibilidad de que los usuarios a\u00f1adan bases de datos H2. Como soluci\u00f3n, es posible bloquear estas vulnerabilidades a nivel de red bloqueando los endpoints `POST /api/database`, `PUT /api/database/:id`, y `POST /api/setup/validateuntil`. Quienes utilicen H2 como base de datos basada en ficheros deber\u00edan migrar a SQLite."
          }
        ],
        "id": "CVE-2023-37470",
        "lastModified": "2026-06-17T06:08:16.987",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 10.0,
                "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"
              },
              "exploitabilityScore": 3.9,
              "impactScore": 6.0,
              "source": "security-advisories@github.com",
              "type": "Secondary"
            },
            {
              "cvssData": {
                "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,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2023-37470",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "yes"
                  },
                  {
                    "technicalImpact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-10-17T14:54:25.239902Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2023-08-04T16:15:09.610",
        "references": [
          {
            "source": "security-advisories@github.com",
            "tags": [
              "Mitigation",
              "Patch",
              "Third Party Advisory"
            ],
            "url": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Mitigation",
              "Patch",
              "Third Party Advisory"
            ],
            "url": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83"
          }
        ],
        "sourceIdentifier": "security-advisories@github.com",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-94"
              }
            ],
            "source": "security-advisories@github.com",
            "type": "Secondary"
          },
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-94"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    },
    "redhat_vex": {
      "current_release_date": "2025-05-28T23:44:08+00:00",
      "cve": "CVE-2023-37470",
      "id": "CVE-2023-37470",
      "initial_release_date": "2023-01-01T00:00:00+00:00",
      "product_status:known_not_affected": "1",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2023/cve-2023-37470.json",
      "version": "3"
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "providerMetadata": {
              "dateUpdated": "2024-08-02T17:16:30.142Z",
              "orgId": "af854a3a-2127-422b-91ae-364da2661108",
              "shortName": "CVE"
            },
            "references": [
              {
                "name": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83",
                "tags": [
                  "x_refsource_CONFIRM",
                  "x_transferred"
                ],
                "url": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83"
              }
            ],
            "title": "CVE Program Container"
          },
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2023-37470",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "total"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2024-10-17T14:54:25.239902Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2024-10-17T14:54:32.130Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "metabase",
              "vendor": "metabase",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 0.43.7.3"
                },
                {
                  "status": "affected",
                  "version": "\u003e= 0.44.0.0, \u003c 0.44.7.3"
                },
                {
                  "status": "affected",
                  "version": "\u003e= 0.45.0.0, \u003c 0.45.4.3"
                },
                {
                  "status": "affected",
                  "version": "\u003e= 0.46.0.0, \u003c 0.46.6.4"
                },
                {
                  "status": "affected",
                  "version": "\u003e= 1.0.0, \u003c 1.43.7.3"
                },
                {
                  "status": "affected",
                  "version": "\u003e= 1.44.0.0, \u003c 1.44.7.3"
                },
                {
                  "status": "affected",
                  "version": "\u003e= 1.45.0.0, \u003c 1.45.4.3"
                },
                {
                  "status": "affected",
                  "version": "\u003e= 1.46.0.0, \u003c 1.46.6.4"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "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."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "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"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-94",
                  "description": "CWE-94: Improper Control of Generation of Code (\u0027Code Injection\u0027)",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2023-08-04T15:12:43.188Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/metabase/metabase/security/advisories/GHSA-p7w3-9m58-rq83"
            }
          ],
          "source": {
            "advisory": "GHSA-p7w3-9m58-rq83",
            "discovery": "UNKNOWN"
          },
          "title": "Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint "
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2023-37470",
        "datePublished": "2023-08-04T15:12:43.188Z",
        "dateReserved": "2023-07-06T13:01:36.998Z",
        "dateUpdated": "2024-10-17T14:54:36.299Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.