Apache Derby: LDAP injection vulnerability in authenticator
Apache Software Foundation Apache Derby
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.derby:derby Maven |
|
Apache Software Foundation Apache Derby
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.derby:derby Maven |
|
10.9.1.0≥ 10.10.1.1 · ≤ 10.10.2.010.11.1.110.12.1.110.13.1.1≥ 10.14.2.0 · < 10.14.2.1≥ 10.16.1.1 · < 10.16.1.2≥ 10.15.1.3 · < 10.15.2.1
|
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 CVE record · apache
A crafted username may bypass authentication checks in LDAP-authenticated Derby installations. An attacker could create junk databases that fill the disk or execute malware accessible to the account that started the Derby server. If a database also lacks SQL GRANT/REVOKE authorization, the attacker could view or corrupt sensitive data and run sensitive functions and procedures.
Operators using LDAP authentication with Maven org.apache.derby:derby should check the affected versions in the 10.1 through 10.16 release families listed in the advisory.