You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contains the core Apache Derby database engine, which also includes the embedded JDBC driver.
Path to dependency file: /spring-distributed-tracing/service-time/pom.xml
Path to vulnerable library: /root/.m2/repository/org/apache/derby/derby/10.14.2.0/derby-10.14.2.0.jar,/root/.m2/repository/org/apache/derby/derby/10.14.2.0/derby-10.14.2.0.jar
Dependency Hierarchy:
flume-ng-embedded-agent-1.9.0.jar (Root Library)
flume-ng-node-1.9.0.jar
flume-jdbc-channel-1.9.0.jar
❌ derby-10.14.2.0.jar (Vulnerable Library)
Found in base branch: master
Vulnerability Details
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.
CVE-2022-46337 - Critical Severity Vulnerability
Vulnerable Library - derby-10.14.2.0.jar
Contains the core Apache Derby database engine, which also includes the embedded JDBC driver.
Path to dependency file: /spring-distributed-tracing/service-time/pom.xml
Path to vulnerable library: /root/.m2/repository/org/apache/derby/derby/10.14.2.0/derby-10.14.2.0.jar,/root/.m2/repository/org/apache/derby/derby/10.14.2.0/derby-10.14.2.0.jar
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
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.
Publish Date: 2023-11-20
URL: CVE-2022-46337
CVSS 3 Score Details (9.8)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://issues.apache.org/jira/browse/DERBY-7147
Release Date: 2023-11-20
Fix Resolution: org.apache.derby:derby:10.14.3,10.15.2.1,10.16.1.2,10.17.1.0
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: