Predictable cryptographic salts via insecure PRNG
Published Apr 2, 2025 · Updated Apr 3, 2025
Weak salt generation in Jonathan Steinert Crypt::Salt 0.01 allows attackers to predict cryptographic salts via insecure randomness. The salt() routine selects every salt character by indexing its alphabet with output from Perl's noncryptographic rand() function. Applications that rely on the module for crypt() salts inherit predictable salt generation, weakening the uniqueness expected from password-hash salts.
Summary
What happened
Weak salt generation in Jonathan Steinert Crypt::Salt 0.01 allows attackers to predict cryptographic salts via insecure randomness. The salt() routine selects every salt character by indexing its alphabet with output from Perl's noncryptographic rand() function. Applications that rely on the module for crypt() salts inherit predictable salt generation, weakening the uniqueness expected from password-hash salts.
The record
- CVE
- CVE-2025-1805
- Published
- Apr 2, 2025
- Updated
- Apr 3, 2025
- Vendor
- Jonathan Steinert
- Product
- Crypt::Salt
- Classifications
- CWE-338
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2025CVE publishedPublication date reported by the CVE source.
- Apr 3, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.01
What conditions does exploitation require?
What is affected?
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