# CVE-2023-51982: CrateDB authentication bypass vulnerability

> Attackers can bypass authentication in CrateDB Admin UI by spoofing the X-Real IP header when local password auth is configured.

- **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:** Yes
- **Published:** 30 Jan 2024
- **Updated:** 29 May 2025
- **Also known as:** GHSA-7mgx-gvjw-m3w3

## What is CVE-2023-51982?

CVE-2023-51982 is a critical authentication bypass vulnerability in n/a, published on 30 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CrateDB 5.5.1 is contains an authentication bypass vulnerability in the Admin UI component. After configuring password authentication and_ Local_ In the case of an address, identity authentication can be bypassed by setting the X-Real IP request header to a specific value and accessing the Admin UI directly using the default user identity.(https://github.com/crate/crate/issues/15231)

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-51982?

8 open source packages ship an affected version, including io.crate:crate. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.crate:crate` | Maven | All versions | 5.2.11 |
| `io.crate:crate` | Maven | All versions | 5.2.11 |
| `io.crate:crate` | Maven | From 5.3.0 | 5.3.8 |
| `io.crate:crate` | Maven | From 5.3.0 | 5.3.8 |
| `io.crate:crate` | Maven | From 5.4.0 | 5.4.7 |
| `io.crate:crate` | Maven | From 5.4.0 | 5.4.7 |
| `io.crate:crate` | Maven | From 5.5.0 | 5.5.2 |
| `io.crate:crate` | Maven | From 5.5.0 | 5.5.2 |

Products: Cratedb Cratedb.

## How do I fix CVE-2023-51982?

Upgrade io.crate:crate to a fixed version for your release line: 5.2.11, 5.3.8, 5.4.7 or 5.5.2.

## Is CVE-2023-51982 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51982 exists.

## Other vulnerabilities in n/a

- [CVE-2024-24565](https://insights.sbomify.com/CVE-2024-24565/): CrateDB database has an arbitrary file read vulnerability (medium 5.7)
- [CVE-2024-37309](https://insights.sbomify.com/CVE-2024-37309/): Client initialized Session-Renegotiation DoS (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51982 and fix it if it is affected.

What it is: CVE-2023-51982 is a critical authentication bypass vulnerability in n/a, published on 30 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51982 exists.

Affected packages and fixed versions:
- io.crate:crate (Maven): affected all versions; fixed in 5.2.11
- io.crate:crate (Maven): affected all versions; fixed in 5.2.11
- io.crate:crate (Maven): affected from 5.3.0; fixed in 5.3.8
- io.crate:crate (Maven): affected from 5.3.0; fixed in 5.3.8
- io.crate:crate (Maven): affected from 5.4.0; fixed in 5.4.7
- io.crate:crate (Maven): affected from 5.4.0; fixed in 5.4.7
- io.crate:crate (Maven): affected from 5.5.0; fixed in 5.5.2
- io.crate:crate (Maven): affected from 5.5.0; fixed in 5.5.2

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-2023-51982/ (Markdown: https://insights.sbomify.com/CVE-2023-51982/index.md)
```

## Sources

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

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