Skip to main content
VulnerabilityPublished Updated

CVE-2022-46337: Apache Derby · LDAP Injection

Affects Apache DerbySource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.4% chance of exploitation in 30 days – higher than 72% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.apache.derby/derbypkg:maven/org.apache.derby/derbyOther threatsAffected
  • =10.1.1.0
  • =10.2.1.6
  • =10.3.1.4
  • =10.4.1.3
  • =10.5.1.1
  • =10.6.1.0
  • =10.7.1.1
  • =10.8.1.2
  • =10.9.1.0
  • =10.10.1.1
  • =10.11.1.1
  • =10.12.1.1
  • =10.13.1.1
  • =10.14.2.0
  • =10.15.1.3
  • =10.16.1.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to Apache Derby version 10.17.1.0 and Java 21 to apply the official fix. 2. For environments unable to upgrade Java, build and deploy custom Derby distributions from the fixed release branches (10.14, 10.15, 10.16) corresponding to their Java LTS version. 3. Implement strict SQL authorization controls (GRANT/REVOKE) in addition to LDAP authentication to limit database access and operations. 4. Monitor Derby server logs for unusual database creation activity or authentication anomalies that could indicate exploitation attempts. 5. Restrict the Derby server process permissions to the minimum necessary, preventing execution of unauthorized code even if the vulnerability is exploited. 6. Employ network segmentation and firewall rules to limit access to Derby servers only to trusted hosts and users. 7. Conduct regular security audits and vulnerability scans focusing on LDAP authentication configurations and Derby deployments. 8. Develop incident response plans that include steps for containment and remediation if exploitation is detected.

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.

References

Community reviews

Loading reviews…