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.
Update org.apache.derby:derby to 10.14.2.1; org.apache.derby:derby to 10.16.1.2; org.apache.derby:derby to 10.15.2.1 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanApache Derby: LDAP injection vulnerability in authenticator affects org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven). Severity is critical. 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.
AI coding agents often install or upgrade packages automatically in maven. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
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.
Update org.apache.derby:derby to 10.14.2.1; org.apache.derby:derby to 10.16.1.2; org.apache.derby:derby to 10.15.2.1 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanApache Derby: LDAP injection vulnerability in authenticator affects org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven), org.apache.derby:derby (maven). Severity is critical. 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.
AI coding agents often install or upgrade packages automatically in maven. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| org.apache.derby:derbymaven | >=10.1.1.0,<=10.1.3.1 | Not reported |
| org.apache.derby:derbymaven | >=10.2.1.6,<=10.2.2.0 | Not reported |
| org.apache.derby:derbymaven | >=10.3.1.4,<=10.3.3.0 | Not reported |
| org.apache.derby:derbymaven | >=10.4.1.3,<=10.4.2.0 | Not reported |
| org.apache.derby:derbymaven | >=10.5.1.1,<=10.5.3.0 | Not reported |
| org.apache.derby:derbymaven | >=10.6.1.0,<=10.6.2.1 | Not reported |
| org.apache.derby:derbymaven | =10.7.1.1 | Not reported |
| org.apache.derby:derbymaven | >=10.8.1.2,<=10.8.3.0 | Not reported |
| org.apache.derby:derbymaven | =10.9.1.0 | Not reported |
| org.apache.derby:derbymaven | >=10.10.1.1,<=10.10.2.0 | Not reported |
| org.apache.derby:derbymaven | =10.11.1.1 | Not reported |
| org.apache.derby:derbymaven | =10.12.1.1 | Not reported |
| org.apache.derby:derbymaven | =10.13.1.1 | Not reported |
| org.apache.derby:derbymaven | =10.14.2.0 | 10.14.2.1 |
| org.apache.derby:derbymaven | =10.16.1.1 | 10.16.1.2 |
| org.apache.derby:derbymaven | >=10.15.1.3,<=10.15.2.0 | 10.15.2.1 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| Package | Affected range | Fixed version |
|---|---|---|
| org.apache.derby:derbymaven | >=10.1.1.0,<=10.1.3.1 | Not reported |
| org.apache.derby:derbymaven | >=10.2.1.6,<=10.2.2.0 | Not reported |
| org.apache.derby:derbymaven | >=10.3.1.4,<=10.3.3.0 | Not reported |
| org.apache.derby:derbymaven | >=10.4.1.3,<=10.4.2.0 | Not reported |
| org.apache.derby:derbymaven | >=10.5.1.1,<=10.5.3.0 | Not reported |
| org.apache.derby:derbymaven | >=10.6.1.0,<=10.6.2.1 | Not reported |
| org.apache.derby:derbymaven | =10.7.1.1 | Not reported |
| org.apache.derby:derbymaven | >=10.8.1.2,<=10.8.3.0 | Not reported |
| org.apache.derby:derbymaven | =10.9.1.0 | Not reported |
| org.apache.derby:derbymaven | >=10.10.1.1,<=10.10.2.0 | Not reported |
| org.apache.derby:derbymaven | =10.11.1.1 | Not reported |
| org.apache.derby:derbymaven | =10.12.1.1 | Not reported |
| org.apache.derby:derbymaven | =10.13.1.1 | Not reported |
| org.apache.derby:derbymaven | =10.14.2.0 | 10.14.2.1 |
| org.apache.derby:derbymaven | =10.16.1.1 | 10.16.1.2 |
| org.apache.derby:derbymaven | >=10.15.1.3,<=10.15.2.0 | 10.15.2.1 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard