OAuth request replay via predictable nonce generation
Published Jan 6, 2025 · Updated Jan 6, 2025
Weak nonce generation in Guzzle OAuth Subscriber before 0.8.1 allows man-in-the-middle attackers to replay OAuth 1.0 requests without TLS. The generateNonce method hashes uniqid output with the request host and path using SHA-1 instead of obtaining the nonce from a cryptographically secure random source. Exploitation requires observation of an unencrypted signed request and successful reuse of its predictable nonce; the documented impact is limited to confidentiality.
Summary
What happened
Weak nonce generation in Guzzle OAuth Subscriber before 0.8.1 allows man-in-the-middle attackers to replay OAuth 1.0 requests without TLS. The generateNonce method hashes uniqid output with the request host and path using SHA-1 instead of obtaining the nonce from a cryptographically secure random source. Exploitation requires observation of an unencrypted signed request and successful reuse of its predictable nonce; the documented impact is limited to confidentiality.
The record
- CVE
- CVE-2025-21617
- Published
- Jan 6, 2025
- Updated
- Jan 6, 2025
- Vendor
- Guzzle
- Product
- Guzzle OAuth Subscriber
- Classifications
- CWE-338, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 6, 2025CVE publishedPublication date reported by the CVE source.
- Jan 6, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.8.1
What conditions does exploitation require?
What is affected?
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