CVE-2025-40905
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWWW::OAuth 1.000 and earlier for Perl uses the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe WWW::OAuth Perl library (versions 1.000 and earlier) uses the built-in rand() function as the default entropy source for cryptographic operations. Since rand() is not cryptographically secure, an attacker could potentially predict or brute-force the randomness used in OAuth token generation, signature creation, or other security-sensitive operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.000CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if WWW::OAuth is installedRun `perl -MWWW::OAuth -e 'print $WWW::OAuth::VERSION'` or `cpan -D WWW::OAuth`Affected if The module is installed and version is 1.000 or earlier
-
Verify the random source used by the librarySearch the WWW::OAuth installation directory for calls to `rand()` in the source files, particularly in files handling token or signature generationAffected if The source code contains `rand()` calls as the default entropy source for cryptographic operations
-
Inspect application code using WWW::OAuthReview your application's code that uses WWW::OAuth to see if it explicitly configures a cryptographically secure random source (CSPRNG)Affected if No explicit CSPRNG configuration is set and the library defaults to using rand()
-
Check for security-sensitive operationsIdentify if your application uses WWW::OAuth for OAuth token generation, access token creation, or signature generationAffected if The library is used to generate tokens, signatures, or other security-sensitive values without a configured secure random source
You are affected if WWW::OAuth version 1.000 or earlier is installed and used for security-sensitive operations without an explicitly configured CSPRNG替代rand().
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to a patched version of WWW::OAuth that uses a cryptographically secure random number generator (CSPRNG) such as Bytes::Random::Secure, or explicitly configure the library to use a secure random source.
Latest version on CPAN (after 1.000) - check metacpan.org for the current stable release
- Run 'cpan -U WWW::OAuth' or 'cpanm WWW::OAuth' to check the currently installed version
- Upgrade WWW::OAuth to the latest available version using 'cpan WWW::OAuth' or 'cpanm WWW::OAuth'
- Verify the upgrade was successful by checking the installed version with 'perldoc WWW::OAuth' or 'perl -MWWW::OAuth -e 'print WWW::OAuth->VERSION'
- Ensure any applications using WWW::OAuth are tested after the upgrade to confirm functionality is intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40905 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-40905 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data