A flaw was found in bouncycastle. The OpenBSDBCrypt.checkPassword utility method compared incorrect data when checking the password allowing incorrect passwords to indicate they were matching with previously hashed ones that were different. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Users unable to upgrade to version 1.67 or greater can copy the `OpenBSDBCrypt.doCheckPassword()` method implementation (https://github.com/bcgit/bc-java/blob/r1rv67/core/src/main/java/org/bouncycastle/crypto/generators/OpenBSDBCrypt.java#L259-L343) into their own utility class and supplement it with the required methods and variables as required
Event History
Dec 18, 2020
CVE Published
12:00 AM
CVE Published
via MITRE·12:52 AM
Data Sourced
via MITRE·12:52 AM
Description
Jan 5, 2021
Data Sourced
via Red Hat·01:58 PM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2020-28052?
CVE-2020-28052 has a high severity rating due to its potential impact on password security.
2
How do I fix CVE-2020-28052?
To fix CVE-2020-28052, update your Bouncy Castle library to version 1.67 or later.
3
What software is affected by CVE-2020-28052?
CVE-2020-28052 affects various packages including eap7-bouncycastle, eap7-activemq-artemis, and others from Red Hat.
4
What is the nature of the vulnerability in CVE-2020-28052?
The vulnerability in CVE-2020-28052 involves incorrect data comparison in password checks, leading to potential authentication bypass.
5
Is CVE-2020-28052 still a risk if my software is updated?
If your software is updated to the recommended versions, the risk associated with CVE-2020-28052 is mitigated.
SecAlerts Pty Ltd. 132 Wickham Terrace Fortitude Valley, QLD 4006, Australia info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.