Approved changes feed: RSS · Atom

cpe:2.3:a:apache:derby:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductDerby (7cdfe75e-c494-57d4-8d26-dc4c16dafdb3)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:apache/db purl2cpe 2026-06-01 10:14:31.055854
pkg:apache/derby purl2cpe 2026-06-01 10:14:31.055856
pkg:deb/debian/derby purl2cpe 2026-06-01 10:14:31.055857
pkg:deb/ubuntu/derby purl2cpe 2026-06-01 10:14:31.055859
pkg:github/apache/derby purl2cpe 2026-06-01 10:14:31.055860
pkg:maven/org.apache.derby/derby purl2cpe 2026-06-01 10:14:31.055862

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-46337 vulnerable 2026-06-08 05:50:38.655418 Apache Derby: LDAP injection vulnerability in authenticator
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.
Published: 2023-11-20T08:49:38.619Z
Updated: 2025-06-10T13:44:34.288Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-1313 vulnerable 2026-06-08 05:11:17.667295 Details available
In Apache Derby 10.3.1.4 to 10.14.1.0, a specially-crafted network packet can be used to request the Derby Network Server to boot a database whose location and contents are under the user's control. If the Derby Network Server is not running with a Java Security Manager policy file, the attack is successful. If the server is using a policy file, the policy file must permit the database location to be read for the attack to work. The default Derby Network Server policy file distributed with the affected releases includes a permissive policy as the default Network Server policy, which allows the attack to work.
Published: 2018-05-07T13:00:00.000Z
Updated: 2024-09-16T16:23:24.352Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2009-4269 vulnerable 2026-06-08 04:51:47.789409 Details available
The password hash generation algorithm in the BUILTIN authentication functionality for Apache Derby before 10.6.1.0 performs a transformation that reduces the size of the set of inputs to SHA-1, which produces a small search space that makes it easier for local and possibly remote attackers to crack passwords by generating hash collisions, related to password substitution.
Published: 2010-08-16T19:00:00.000Z
Updated: 2024-08-07T06:54:10.308Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2005-4849 vulnerable 2026-06-08 04:48:45.351949 Details available
Apache Derby before 10.1.2.1 exposes the (1) user and (2) password attributes in cleartext via (a) the RDBNAM parameter of the ACCSEC command and (b) the output of the DatabaseMetaData.getURL function, which allows context-dependent attackers to obtain sensitive information.
Published: 2007-07-05T20:00:00.000Z
Updated: 2024-09-16T23:56:48.968Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.