Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🔐 CVE-2022-46337: pkg:maven/org.apache.derby/[email protected] #51

Closed
github-actions bot opened this issue Nov 22, 2023 · 0 comments · Fixed by #52
Closed

🔐 CVE-2022-46337: pkg:maven/org.apache.derby/[email protected] #51

github-actions bot opened this issue Nov 22, 2023 · 0 comments · Fixed by #52
Assignees
Labels
security Security related change

Comments

@github-actions
Copy link

Summary

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: CVE-2022-46337
CWE: CWE-94

References

@github-actions github-actions bot added the security Security related change label Nov 22, 2023
@kaklakariada kaklakariada self-assigned this Dec 19, 2023
kaklakariada added a commit that referenced this issue Dec 19, 2023
kaklakariada added a commit that referenced this issue Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security Security related change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant