CVE-2022-46337: Apache Derby: LDAP injection vulnerability in authenticator

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 1.4%, percentile 73: FIRST’s model estimates a 1.4% chance of exploitation activity in the next 30 days, higher than 73% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes org.apache.derby:derby (Maven) >= 10.1.1.0, <= 10.1.3.1, no fixed version listed; org.apache.derby:derby (Maven) >= 10.2.1.6, <= 10.2.2.0, no fixed version listed; org.apache.derby:derby (Maven) >= 10.3.1.4, <= 10.3.3.0, no fixed version listed; org.apache.derby:derby (Maven) >= 10.4.1.3, <= 10.4.2.0, no fixed version listed. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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.

Weakness type: CWE-74, CWE-94.

Product: org.apache.derby:derby (Maven) · Assigned by: apache · Published: 2023-11-20

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 1.42% probability of exploitation activity in the next 30 days; percentile 73.

Timeline

• 2023-11-20 — CVE record published by apache
• 2023-11-20 — GitHub-reviewed advisory GHSA-rcjc-c4pj-xxrp published (critical)
• 2025-06-10 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. lists.apache.org lists.apache.org

Vulnerability records

1. GitHub Advisory GHSA-rcjc-c4pj-xxrp github.com
2. CVE.org record CVE-2022-46337 cve.org
3. NVD entry CVE-2022-46337 nvd.nist.gov

Other references from the CVE record and advisory

1. issues.apache.org issues.apache.org

Critical Maven advisories · Today’s Security Digest