Cleartext password recovery via premature bcrypt truncation
Published Nov 3, 2023 · Updated Sep 12, 2024
Incorrect bcrypt hashing in Botan 1.11.0 through 2.0.1 allows attackers to recover long cleartext passwords with reduced effort. The bcrypt implementation truncates passwords at 56 characters instead of bcrypt's 72-character limit, ignoring the final bytes during hashing. Exploitation requires access to a stored bcrypt hash for a 57-to-72-character password; the flaw weakens confidentiality without changing data or availability.
Summary
What happened
Incorrect bcrypt hashing in Botan 1.11.0 through 2.0.1 allows attackers to recover long cleartext passwords with reduced effort. The bcrypt implementation truncates passwords at 56 characters instead of bcrypt's 72-character limit, ignoring the final bytes during hashing. Exploitation requires access to a stored bcrypt hash for a 57-to-72-character password; the flaw weakens confidentiality without changing data or availability.
The record
- CVE
- CVE-2017-7252
- Published
- Nov 3, 2023
- Updated
- Sep 12, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-319, T1110.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 3, 2023CVE publishedPublication date reported by the CVE source.
- Sep 12, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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