CVE-2025-1828
Timlegge Crypt\ \
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-1828 is a high-severity Insufficient Entropy (CWE-331) vulnerability in Timlegge Crypt\. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-12 (Cryptographic Key Establishment and Management) and SC-13 (Cryptographic Protection) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-1828 affects the Crypt::Random Perl package in versions 1.05 through 1.55, where it may use the Perl rand() function—which is not cryptographically strong—for generating random values in cryptographic functions. This occurs when no Provider is specified and strong entropy sources like /dev/urandom or an Entropy Gathering Daemon (EGD) service are unavailable, causing the package to default to the insecure Crypt::Random::rand provider. Windows versions of Perl are particularly susceptible to this issue by default.
Attackers can exploit this vulnerability remotely with low complexity and no privileges required, though it necessitates user interaction such as running malicious or affected Perl scripts. Successful exploitation generates predictable random values, leading to high impacts on confidentiality, integrity, and availability (CVSS 8.8: AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), potentially enabling attacks like key prediction, nonce reuse, or forgery in cryptographic operations dependent on the module. Associated weaknesses include CWE-331 (Insufficient Entropy) and CWE-338 (Use of Cryptographically Weak PRNG).
Mitigation involves updating Crypt::Random to a patched version, as indicated by fixes in the Crypt-OpenPGP repository, including commit 1f8b29e9e89d8d083fd025152e76ec918136cc05 and pull request 1. Users should also explicitly specify a secure Provider or ensure availability of /dev/urandom or EGD services, avoiding reliance on the default rand() behavior documented in Perl's rand function reference.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-7415
Vulnerability Data
Crypt::Random Perl package 1.05 through 1.55 may use rand() function, which is not cryptographically strong, for cryptographic functions. If the Provider is not specified and /dev/urandom or an Entropy Gathering Daemon (egd) service is not available Crypt::Random will default to…
more
use the insecure Crypt::Random::rand provider. In particular, Windows versions of perl will encounter this issue by default.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 9 hardening rules · 4 OS baselines
V6.5.2V11.3.4V7.2.3V11.5.1
Mitigating Controls (NIST 800-53 r5) AI
Requiring specific approved cryptography for protection directly mandates use of strong PRNGs instead of weak ones.
Key establishment and management requirements force use of approved RNG sources with adequate entropy when generating keys.
Security engineering principles can include selection of strong entropy sources during design.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices explicitly include vetted RNG and entropy sources, directly preventing this weakness while covering many other development concerns.
Password-strength policies implicitly require sufficient entropy, but the control addresses authentication rather than algorithmic randomness.
Proper encryption for data-at-rest requires sufficient entropy for keys/nonces; eliminating the weakness therefore supports but does not fully realize the control.
Cryptographic protection of data-in-transit depends on adequate entropy; the weakness directly undermines the control's effectiveness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Mandates use of cryptography that must rely on sufficient entropy sources.
Security testing can detect insufficient-entropy defects before release.
Secure-SDLC activities include entropy validation during design and testing.
Application security requirements can specify cryptographically strong random number generation.
Secure engineering principles include selection of appropriate cryptographic primitives.
Secure-coding rules can explicitly forbid weak random-number generation.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-331
- V-248563 The OL 8 SSH server must be configured to use strong entropy. prevents CWE-331, CWE-338
RHEL 7 (1 rule)
- V-204497 The Red Hat Enterprise Linux operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-331
RHEL 8 (2 rules)
- V-230223 RHEL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-331
- V-230253 RHEL 8 must ensure the SSH server uses strong entropy. prevents CWE-338
Ubuntu 22.04 (1 rule)
- V-260650 Ubuntu 22.04 LTS must implement NIST FIPS-validated cryptography to protect classified information and for the following: To provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-338