CVE-2026-5088: CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator in JDEGUEST Apache::API::Password
Apache::API::Password versions through 0.5.2 for Perl can generate insecure random values for salts. The _make_salt and _make_salt_bcrypt methods will attept to load Crypt::URandom and then Bytes::Random::Secure to generate random bytes for the salt. If those modules are unavailable, it will simply return 16 bytes generated with Perl's built-in rand function. The rand function is unsuitable for cryptographic use. These salts are used for password hashing.
AI Analysis
Technical Summary
Apache::API::Password versions up to 0.5.2 for Perl attempt to generate salts for password hashing using Crypt::URandom or Bytes::Random::Secure modules. If these modules are not present, the code uses Perl's built-in rand function to generate 16-byte salts. Since rand is not cryptographically secure, this results in weak salts that can undermine the strength of password hashes. This vulnerability is classified as CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator).
Potential Impact
The use of a weak pseudo-random number generator for salt generation can lead to predictable salts, which may facilitate precomputation or rainbow table attacks against password hashes. This reduces the confidentiality of user credentials by weakening the effectiveness of the password hashing mechanism. The CVSS score of 7.5 (high) reflects the network attack vector with no privileges or user interaction required and a high impact on confidentiality.
Mitigation Recommendations
No official patch or remediation guidance is currently available from the vendor. Users should ensure that the Crypt::URandom or Bytes::Random::Secure Perl modules are installed and available in their environment to avoid fallback to the insecure rand function. Monitor the vendor advisory for updates or official fixes. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
CVE-2026-5088: CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator in JDEGUEST Apache::API::Password
Description
Apache::API::Password versions through 0.5.2 for Perl can generate insecure random values for salts. The _make_salt and _make_salt_bcrypt methods will attept to load Crypt::URandom and then Bytes::Random::Secure to generate random bytes for the salt. If those modules are unavailable, it will simply return 16 bytes generated with Perl's built-in rand function. The rand function is unsuitable for cryptographic use. These salts are used for password hashing.
CVSS v3.1
Score 7.5high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Apache::API::Password versions up to 0.5.2 for Perl attempt to generate salts for password hashing using Crypt::URandom or Bytes::Random::Secure modules. If these modules are not present, the code uses Perl's built-in rand function to generate 16-byte salts. Since rand is not cryptographically secure, this results in weak salts that can undermine the strength of password hashes. This vulnerability is classified as CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator).
Potential Impact
The use of a weak pseudo-random number generator for salt generation can lead to predictable salts, which may facilitate precomputation or rainbow table attacks against password hashes. This reduces the confidentiality of user credentials by weakening the effectiveness of the password hashing mechanism. The CVSS score of 7.5 (high) reflects the network attack vector with no privileges or user interaction required and a high impact on confidentiality.
Mitigation Recommendations
No official patch or remediation guidance is currently available from the vendor. Users should ensure that the Crypt::URandom or Bytes::Random::Secure Perl modules are installed and available in their environment to avoid fallback to the insecure rand function. Monitor the vendor advisory for updates or official fixes. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-03-28T19:31:47.729Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69df426b82d89c981f9c89ce
Added to database: 4/15/2026, 7:46:51 AM
Last enriched: 5/2/2026, 1:56:56 AM
Last updated: 5/30/2026, 12:55:06 AM
Views: 77
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.