Predictable cryptographic output via insecure rand fallback
Published Mar 10, 2025 · Updated Sep 9, 2025
Weak random-number generation in Perl Crypt::Random 1.05 through 1.55 allows attackers to predict cryptographic output. Crypt::Random::Provider::rand passes byte-generation requests to Perl's internal rand() function instead of an operating-system entropy source. The fallback is selected when no provider is specified and neither /dev/urandom nor EGD is available; Windows Perl encounters that state by default.
Summary
What happened
Weak random-number generation in Perl Crypt::Random 1.05 through 1.55 allows attackers to predict cryptographic output. Crypt::Random::Provider::rand passes byte-generation requests to Perl's internal rand() function instead of an operating-system entropy source. The fallback is selected when no provider is specified and neither /dev/urandom nor EGD is available; Windows Perl encounters that state by default.
The record
- CVE
- CVE-2025-1828
- Published
- Mar 10, 2025
- Updated
- Sep 9, 2025
- Vendor
- Perl
- Product
- Crypt::Random
- Classifications
- CWE-338, CWE-331
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2025CVE publishedPublication date reported by the CVE source.
- Sep 9, 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=1.05 <1.56
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