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.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
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
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 | 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 |
2 more packages
io.crate:crate Maven | From 5.5.0 | 5.5.2 |
io.crate:crate Maven | From 5.5.0 | 5.5.2 |
Products include 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.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
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
Sources
Also known as GHSA-7mgx-gvjw-m3w3.