CVE-2025-15618
CriticalSummary
Wersje Business::OnlinePayment::StoredTransaction do 0.01 dla Perla wykorzystują niebezpieczny klucz tajny. Klucz ten jest generowany przy użyciu hasha MD5 z pojedynczego wywołania wbudowanej funkcji rand, co jest niewłaściwe do zastosowań kryptograficznych.
Risk Assessment
Użycie nieodpowiedniego klucza tajnego do szyfrowania danych transakcji kartą kredytową naraża organizację na ryzyko wycieku wrażliwych informacji finansowych.
Recommendation
Zaleca się aktualizację do nowszej wersji Business::OnlinePayment::StoredTransaction, która stosuje bezpieczniejsze metody generowania kluczy tajnych.
Related vulnerabilities
- CVE-2026-96207Critical
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
- CVE-2026-94510Critical
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.
- CVE-2026-88131Critical
Deserialization of untrusted data in Microsoft Dataverse allows an unauthorized attacker to execute code over a network.
- CVE-2026-77900Critical
Missing authentication for a critical function in Azure App Service allows an unauthorized attacker to execute code over a network.
- CVE-2026-69435Critical
Missing authorization in Azure SRE Agent allows an authorized attacker to elevate privileges over a network.
- CVE-2026-84249Critical
IBM Guardium Data Protection 12.2 and 12.2.2 could allow a remote attacker to execute arbitrary management operations due to missing authentication for a critical function.
- CVE-2026-80381Critical
IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a remote attacker to execute unauthorized SQL statements due to SQL injection.
- CVE-2026-75875Critical
IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a remote attacker to execute arbitrary code due to path traversal.
- CVE-2026-107726Critical
Hazelcast prior to 5.4.5, 5.5.10, and 5.6.1 contains improper validation of data supplied by a malicious client able to connect to a cluster, allowing arbitrary reads from a cluster member's Java heap, off-heap data, and JVM process address space. The same flaw can crash cluster members and, in some Hazelcast Enterprise Edition configurations, corrupt memory with possible arbitrary code execution. This issue is fixed in versions 5.4.5, 5.5.10, 5.6.1, and 5.7.0.
- CVE-2026-107722Critical
fast-jwt from 6.2.0 until 6.3.0 can misclassify RSA public-key text as an HMAC secret when the key has non-whitespace content before its PEM header. In src/crypto.js, performDetectPublicKeyAlgorithms trims whitespace but publicKeyPemMatcher remains start-anchored, so comments, control characters, zero-width characters, or wrapper text can prevent PEM detection and reach the HMAC fallback. An attacker who knows the public key bytes can sign arbitrary HS256 claims with that public material when HS256 is inferred or allowed, resulting in authentication or authorization bypass. An asymmetric-only algorithm allowlist prevents the attack. This issue is fixed in version 6.3.0.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

