Predictable OAuth nonces via 32-bit weak PRNG
Published Jan 3, 2025 · Updated Jan 21, 2025
Weak nonce generation in Net::OAuth::Client before 0.29 allows attackers to predict default OAuth nonces via a 32-bit PRNG. The _make_request method assigns int(rand(2**32)) when no nonce is supplied, limiting the value to a non-cryptographic 32-bit space. Exposure requires an application to rely on the generated default rather than supplying its own nonce; published sources establish weakened request uniqueness but no concrete downstream attack.
Summary
What happened
Weak nonce generation in Net::OAuth::Client before 0.29 allows attackers to predict default OAuth nonces via a 32-bit PRNG. The _make_request method assigns int(rand(2**32)) when no nonce is supplied, limiting the value to a non-cryptographic 32-bit space. Exposure requires an application to rely on the generated default rather than supplying its own nonce; published sources establish weakened request uniqueness but no concrete downstream attack.
The record
- CVE
- CVE-2025-22376
- Published
- Jan 3, 2025
- Updated
- Jan 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-338
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2025CVE publishedPublication date reported by the CVE source.
- Jan 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo