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
A cleverly devised username might bypass LDAP authentication checks in versions prior to 10.14.3, 10.15.0.x prior to 10.15.2.1, 10.16.0.x prior to 10.16.1.2, and 10.17.0.x prior to 10.17.1.0. 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. 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. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.
Additional Info Attack vector: NETWORK Attack complexity: LOW Confidentiality impact: HIGH Availability impact: HIGH Remediation Upgrade Recommendation: 10.17.1.0
The text was updated successfully, but these errors were encountered:
Checkmarx (SCA): Vulnerable Package
Vulnerability: Read More about CVE-2022-46337
Checkmarx Project: SamHeadrickCx/easybuggy4sb
Repository URL: https://github.com/SamHeadrickCx/easybuggy4sb
Branch: master
Scan ID: 94cbf8fd-fbe8-49c7-9c55-da0658f9cbfc
A cleverly devised username might bypass LDAP authentication checks in versions prior to 10.14.3, 10.15.0.x prior to 10.15.2.1, 10.16.0.x prior to 10.16.1.2, and 10.17.0.x prior to 10.17.1.0. 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. 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. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.
Additional Info
Attack vector: NETWORK
Attack complexity: LOW
Confidentiality impact: HIGH
Availability impact: HIGH
Remediation Upgrade Recommendation: 10.17.1.0
The text was updated successfully, but these errors were encountered: