Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-7mgx-gvjw-m3w3

HIGH

CrateDB authentication bypass vulnerability

Also known asCVE-2023-51982
Published
Jan 30, 2024
Updated
Nov 21, 2024
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk50th percentile+0.69%
0.00%0.41%0.82%1.23%0.0%0.7%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected
io.crate:crateio.crate:crateio.crate:crateio.crate:crate

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.crate:crateall versions5.2.11
Mavenio.crate:crate5.3.0&&< 5.3.85.3.8
Mavenio.crate:crate5.4.0&&< 5.4.75.4.7
Mavenio.crate:crate5.5.0&&< 5.5.25.5.2
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.crate:crate. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update io.crate:crate to 5.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7mgx-gvjw-m3w3 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-7mgx-gvjw-m3w3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7mgx-gvjw-m3w3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-7mgx-gvjw-m3w3 in your dependencies?

O3 detects GHSA-7mgx-gvjw-m3w3 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.