Information exposure via weak password hash verification
Published Dec 28, 2021 · Updated Aug 4, 2024
Cryptographic weakness in Maddy before 0.5.2 allows remote attackers to expose sensitive information through password authentication. The shadow authentication verifier passes stored hashes to crypt.NewFromHash after registering APR1 and MD5-crypt, thereby accepting weak MD5-based password hashes. Exposure requires the shadow backend to contain such a hash; published sources do not identify the remotely observable data, limiting the established consequence to confidentiality loss.
Summary
What happened
Cryptographic weakness in Maddy before 0.5.2 allows remote attackers to expose sensitive information through password authentication. The shadow authentication verifier passes stored hashes to crypt.NewFromHash after registering APR1 and MD5-crypt, thereby accepting weak MD5-based password hashes. Exposure requires the shadow backend to contain such a hash; published sources do not identify the remotely observable data, limiting the established consequence to confidentiality loss.
The record
- CVE
- CVE-2021-42583
- Published
- Dec 28, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 28, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo