CVE-2025-2814VulnerabilityPublished 12 Apr 2025Updated 5 Sep 2025

CVE-2025-2814: LDS Crypt::CBC · PRNG

Affects LDS Crypt::CBCSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
LDS Crypt::CBC	Affected =1.21	Fixed in–

AI-suggested

European organizations should first identify all instances of Crypt::CBC usage in their Perl environments, especially versions between 1.21 and 3.05. They should verify the operating system's availability of secure entropy sources like /dev/urandom. If /dev/urandom is unavailable, organizations should consider the following mitigations: 1) Upgrade Crypt::CBC to a version that explicitly uses a cryptographically secure PRNG or patches this vulnerability once available. 2) Where upgrading is not immediately possible, implement custom entropy sources or wrappers to ensure secure random number generation, such as integrating with CPAN modules that provide secure randomness (e.g., Crypt::Random). 3) Restrict local access to systems running vulnerable versions to trusted personnel only, minimizing the risk of local exploitation. 4) Conduct code audits to ensure that cryptographic keys and IVs are not generated using insecure methods. 5) For embedded or legacy systems, consider OS-level upgrades or configurations that provide secure entropy sources. 6) Monitor for updates from the vendor or CPAN security advisories and apply patches promptly. 7) Implement defense-in-depth by combining cryptographic best practices with system hardening and access controls.

Description

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 will fallback to use the insecure rand() function.

Impact

For European organizations, the impact of this vulnerability depends on the deployment context of Crypt::CBC in Perl-based applications, especially those running on operating systems lacking /dev/urandom. Organizations using legacy or specialized systems (e.g., embedded devices, certain industrial control systems, or constrained environments) may be at higher risk. The use of a weak PRNG can lead to predictable cryptographic outputs, which could allow attackers with local access to compromise the reliability of encryption, potentially causing service disruptions or enabling further cryptographic attacks. Although the CVSS score indicates limited impact on confidentiality and integrity, the availability impact could affect critical services relying on secure cryptographic operations. This is particularly relevant for sectors such as finance, healthcare, and critical infrastructure in Europe, where Perl is still used in legacy systems or automation scripts. Additionally, the lack of secure entropy sources in some environments may be more prevalent in certain operational contexts, increasing exposure. However, since exploitation requires local access and the absence of /dev/urandom, the overall risk to large-scale internet-facing services is limited.

CWE-338Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.
Implementation
Use functions or hardware which use a hardware-based random number generation for all crypto. This is the recommended solution. Use CyptGenRandom on Windows, or hw_rand() on Linux.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
OWASP ASVS 4.0.3
V6.3.3 (opens in a new tab)
V6.3.2 (opens in a new tab)
V6.3.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-329Generation of Predictable IV with CBC Mode (opens in a new tab)
Variant weaknessLikelihood of exploit: MediumOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product generates and uses a predictable initialization Vector (IV) with Cipher Block Chaining (CBC) Mode, which causes algorithms to be susceptible to dictionary attacks when they are encrypted under the same key.
Implementation
NIST recommends two methods of generating unpredictable IVs for CBC mode. The first is to generate the IV randomly. The second method is to encrypt a nonce with the same key and cipher to be used to encrypt the plaintext.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-331Insufficient Entropy (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
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.
Implementation
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.
OWASP Cheat Sheets
Session Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V3.2.2 (opens in a new tab)
V3.2.4 (opens in a new tab)
V2.3.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Sep 2025, 20:13 UTC

WeaknessesCWE-338, CWE-329, CWE-331

Technical details

References

Community reviews

Related threats