Cryptographic output prediction via rand-seeded default entropy
Published Mar 28, 2025 · Updated Sep 5, 2025
Weak random generation in Robert Rothenberg Data::Entropy 0.007 and earlier allows local users to predict cryptographic output. When no entropy source is configured, entropy_source builds a 32-byte key for its AES counter-mode default by concatenating outputs from Perl's non-cryptographic CORE::rand function. Exposure requires a consuming Perl program to rely on that default; predictable entropy can compromise secrets or cryptographic values that the program generates.
Summary
What happened
Weak random generation in Robert Rothenberg Data::Entropy 0.007 and earlier allows local users to predict cryptographic output. When no entropy source is configured, entropy_source builds a 32-byte key for its AES counter-mode default by concatenating outputs from Perl's non-cryptographic CORE::rand function. Exposure requires a consuming Perl program to rely on that default; predictable entropy can compromise secrets or cryptographic values that the program generates.
The record
- CVE
- CVE-2025-1860
- Published
- Mar 28, 2025
- Updated
- Sep 5, 2025
- Vendor
- Robert Rothenberg
- Product
- Data::Entropy
- Classifications
- CWE-331, CWE-338
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 28, 2025CVE publishedPublication date reported by the CVE source.
- Sep 5, 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 <0.008
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