# CVE-2024-24213: SQL injection in n/a

> A SQL injection vulnerability in Supabase PostgreSQL allows authorized users to execute arbitrary queries via the dashboard, though the vendor considers this an intended feature.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2024
- **Updated:** 19 Aug 2024
- **Also known as:** BIT-postgresql-2024-24213, GHSA-vq84-wx4w-6r76

## What is CVE-2024-24213?

CVE-2024-24213 is a critical SQL injection vulnerability in n/a, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Supabase PostgreSQL v15.1 was discovered to contain a SQL injection vulnerability via the component /pg_meta/default/query. NOTE: the vendor's position is that this is an intended feature; also, it exists in the Supabase dashboard product, not the Supabase PostgreSQL product. Specifically, /pg_meta/default/query is for SQL queries that are entered in an intended UI by an authorized user. Nothing is injected.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-24213?

1 open source package ship an affected version, including postgresql. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `postgresql` | Bitnami | From 15.1.0 to 15.1.0 | None |

Products: Supabase Postgres.

## How do I fix CVE-2024-24213?

No fix has been published for CVE-2024-24213 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-24213 being exploited?

There is no known exploitation of CVE-2024-24213 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24213 and fix it if it is affected.

What it is: CVE-2024-24213 is a critical SQL injection vulnerability in n/a, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-24213 in the wild and no public exploit code.

Affected packages and fixed versions:
- postgresql (Bitnami): affected from 15.1.0 up to 15.1.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-24213/ (Markdown: https://insights.sbomify.com/CVE-2024-24213/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-24213
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-24213
- OSV: https://osv.dev/vulnerability/CVE-2024-24213

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-24213/
Summaries are generated and may contain mistakes; the official description above is the record.