Cyber Resilience

CVE-2025-2814

Published
13 April 2025
Modified
15 April 2026
CVSS Score v3.1 4.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0019 9th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-2814 is a medium-severity Generation of Predictable IV with CBC Mode (CWE-329) vulnerability. Its CVSS base score is 4.0 (Medium).

Operationally, ranked at the 9th 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.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

Crypt::CBC versions between 1.21 and 3.05 for Perl may use the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions. This issue affects operating systems where "/dev/urandom'" is unavailable. In that case, Crypt::CBC…

more

will fallback to use the insecure rand() function.

CWE(s)
CWE-329CWE-331CWE-338

Related Threats

CVEs Like This One

CVE-2025-67504Shared CWE-331, CWE-338
CVE-2024-57868Shared CWE-331, CWE-338
CVE-2025-1828Shared CWE-331, CWE-338
CVE-2024-58040Shared CWE-331, CWE-338
CVE-2024-58036Shared CWE-331, CWE-338
CVE-2024-52322Shared CWE-331, CWE-338
CVE-2024-56370Shared CWE-331, CWE-338
CVE-2025-1860Shared CWE-331, CWE-338
CVE-2025-66565Shared CWE-331, CWE-338
CVE-2026-42155Shared CWE-331, CWE-338

Affected Assets

—
CBC
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-13 Cryptographic Protection
  • SC-12 Cryptographic Key Establishment and Management
  • CM-6 Configuration Settings
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 10 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V11.6.1
  • V6.5.2
  • V11.3.4
  • V7.2.3

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match
prevent

Directly requires that cryptography be implemented using FIPS-validated or NSA-approved modules and algorithms that rely on cryptographically secure entropy sources rather than rand().

SC-12 Cryptographic Key Establishment and Management good match
prevent

Mandates proper cryptographic key establishment and management, which includes use of approved random-bit generators instead of the non-cryptographic rand() fallback.

CM-6 Configuration Settings partial match
prevent

Requires configuration settings that enforce approved cryptographic parameters and disable insecure entropy sources such as rand() when /dev/urandom is unavailable.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce correct cryptographic implementation such as random IV generation for CBC.

PR.AA-03 partial match
prevents

Password-strength policies implicitly require sufficient entropy, but the control addresses authentication rather than algorithmic randomness.

PR.DS-01 partial match
prevents

Proper encryption for data-at-rest requires sufficient entropy for keys/nonces; eliminating the weakness therefore supports but does not fully realize the control.

PR.DS-02 partial match
prevents

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.

A.8.24 Use of cryptography full match
prevents

Mandates proper cryptographic controls including IV generation, directly preventing predictable-IV CBC weaknesses.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development can detect predictable IV usage before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC processes catch cryptographic flaws like bad IVs during design and review phases.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify cryptographically strong random number generation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles guide selection of strong cryptographic primitives and IV handling.

A.8.28 Secure coding partial match
prevents

Requires secure coding practices that eliminate predictable IV usage in CBC implementations.

Hardening callouts derived

Configuration rules from DISA STIG baselines that reduce the attack surface for weaknesses of the type cited by this CVE. Derived transitively via CVE→CWE→STIG over `controls_xwalks` (authoritative rows only).

Oracle Linux 8 (1 rule)
  • 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. via CWE-331
RHEL 8 (1 rule)
  • 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. via CWE-331

References