Skip to main content

Business EUVDEUVD-2025-209143

| CVE-2025-15618 CRITICAL
Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) (CWE-338)
2026-03-31 CPANSec GHSA-7rq2-v6rc-96jw
9.1
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Cryptographic PRNG selection
Impact

Despite the absence of a CVSS score, this vulnerability carries extreme real-world risk. The attack vector is local or network-based depending on deployment, requires no authentication, and directly undermines the confidentiality of encrypted credit card data-the core security function of the library. Unlike high-CVSS-but-low-impact issues, this represents authentic, material risk: any encrypted transaction using a derived key is potentially recoverable through key space exhaustion or statistical analysis. The predictability of rand() combined with MD5's known collision properties means an attacker with access to encrypted payloads can systematically recover keys. The vulnerability affects financial transaction processing, triggering regulatory obligations (PCI DSS, etc.). Absence of KEV status does not diminish severity; this is a foundational cryptographic failure in a payment security library.

Exploit ScenarioDerived

An attacker who gains access to encrypted credit card data stored by a vulnerable Business::OnlinePayment::StoredTransaction installation can exploit the weak key generation. Since the secret key is derived from MD5(rand()), the attacker can enumerate the limited key space by replaying known rand() sequences or using statistical properties of Perl's PRNG to narrow possibilities. With computational resources, the attacker recovers encryption keys and decrypts stored transaction records, compromising card numbers, expiration dates, and other sensitive payment data without requiring authentication or network access to the generating system.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 31, 2026

Business::OnlinePayment::StoredTransaction through version 0.01 uses cryptographically weak secret key generation based on MD5 hashing of a single rand() call, exposing encrypted credit card transaction data to key recovery attacks. The vulnerability affects Perl module users who rely on this library for payment processing, allowing attackers to potentially decrypt stored transaction records. No CVSS score was assigned, but the direct compromise of payment card encryption represents critical risk to financial data confidentiality.

RemediationAI

Upgrade to a patched version of Business::OnlinePayment::StoredTransaction beyond 0.01 that implements cryptographically secure key generation (e.g., using /dev/urandom or Crypt::Random). A security patch is available at https://security.metacpan.org/patches/B/Business-OnlinePayment-StoredTransaction/0.01/CVE-2025-15618-r1.patch. For immediate mitigation, review stored transaction records encrypted with version 0.01 keys; consider re-encrypting sensitive data with a corrected implementation using strong random number generation (e.g., Crypt::OpenSSL::Random) instead of rand(). Audit all systems using this module in production payment processing environments and apply patches immediately before processing new transactions.

Affected VersionsENISA

Business::OnlinePayment::StoredTransaction 0 ≤0.01

Affected Packages

euvd business_onlinepayment_storedtransaction no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Business::OnlinePayment::StoredTransaction Perl module implements encryption of credit card transaction data for secure storage. The vulnerability stems from CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator), where the secret key is derived from MD5(rand()), combining two fatal cryptographic weaknesses: Perl's built-in rand() function is a weak pseudo-random number generator unsuitable for security purposes (predictable, low entropy), and MD5 is cryptographically broken for key derivation. The module generates these keys for protecting sensitive payment card information, making the weak key generation directly exploitable against financial data.

Know when Business gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

DescriptionCVE.org

Business::OnlinePayment::StoredTransaction versions through 0.01 for Perl uses an insecure secret key.

Business::OnlinePayment::StoredTransaction generates a secret key by using a MD5 hash of a single call to the built-in rand function, which is unsuitable for cryptographic use.

This key is intended for encrypting credit card transaction data.

Threat Intelligence Overview

EPSS Score
0.0%
Top 94% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy