Data::Entropy: Insufficient Entropy
CVE-2025-1860 is a high-severity insufficient entropy vulnerability in Data::Entropy from ZEFRAM, with a CVSS 3.1 base score of 7.7 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists version 0.008 as the first without the flaw, so updating Data::Entropy to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.19% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Data::Entropy to 0.008 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| ZEFRAM | Data::Entropy | before 0.008 | 0.008 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CISA (ADP).
Official description
Data::Entropy for Perl 0.007 and earlier use the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insufficient Entropy
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
How developers prevent this class of flaw
- Determine the necessary entropy to adequately provide for randomness and predictability. This can be achieved by increasing the number of bits of objects such as keys and seeds.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Insufficient Entropy vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 8.2 High severity
- 8.0 High severity
- 9.8 Critical severity
- 9.1 Critical severity
Spotted an error? Tell us.