Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

GHSA-rcjc-c4pj-xxrp — derby

CRITICAL

GHSA-rcjc-c4pj-xxrp is a critical-severity (CVSS 9.8) CWE-74 vulnerability in org.apache.derby:derby. A fix is available for org.apache.derby:derby — see the affected versions and patch details below.

Apache Derby: LDAP injection vulnerability in authenticator

Also known asCVE-2022-46337
Published
Nov 20, 2023
Updated
Sep 10, 2026
Affected
16 pkgs
Patched
3 / 16
Exploits
None indexed
Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rcjc-c4pj-xxrp.

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

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.

How urgent is this, really

GHSA-rcjc-c4pj-xxrp plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

16 pkgs affected
☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby☕org.apache.derby:derby+8 more

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

A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren't also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures.

Mitigation:

Users should upgrade to Java 21 and Derby 10.17.1.0.

Alternatively, users who wish to remain on older Java versions should build their own Derby distribution from one of the release families to which the fix was backported: 10.16, 10.15, and 10.14. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.

Affected Packages

16 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.derby:derby≥ 10.1.1.0No fix
☕Mavenorg.apache.derby:derby≥ 10.2.1.6No fix
☕Mavenorg.apache.derby:derby≥ 10.3.1.4No fix
☕Mavenorg.apache.derby:derby≥ 10.4.1.3No fix
☕Mavenorg.apache.derby:derby≥ 10.5.1.1No fix
☕Mavenorg.apache.derby:derby≥ 10.6.1.0No fix

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.derby:derby, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    No patched version of org.apache.derby:derby has shipped for GHSA-rcjc-c4pj-xxrp yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rcjc-c4pj-xxrp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rcjc-c4pj-xxrp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren't also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures. Mitigat
O3 Security · Impact-Aware SCA

Is GHSA-rcjc-c4pj-xxrp in your dependencies?

O3 Security finds GHSA-rcjc-c4pj-xxrp across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works
GHSA-rcjc-c4pj-xxrp: derby (Critical 9.8) | O3 Security