Token prediction via weak random_string generation
Published Mar 28, 2026 · Updated Mar 28, 2026
Predictable token generation in Tokuhiro Matsuno Amon2 before 6.17 allows remote attackers to predict session and CSRF tokens. Amon2::Util::random_string uses rand() directly before 6.04; versions 6.04 and 6.05 rely solely on /dev/urandom, while 6.06 through 6.16 fall back to SHA-1 output seeded with rand(), the PID, and guessable time. Exposure depends on applications using the function for session IDs, cookie secrets, or CSRF tokens; successful prediction permits token forgery or session compromise.
Summary
What happened
Predictable token generation in Tokuhiro Matsuno Amon2 before 6.17 allows remote attackers to predict session and CSRF tokens. Amon2::Util::random_string uses rand() directly before 6.04; versions 6.04 and 6.05 rely solely on /dev/urandom, while 6.06 through 6.16 fall back to SHA-1 output seeded with rand(), the PID, and guessable time. Exposure depends on applications using the function for session IDs, cookie secrets, or CSRF tokens; successful prediction permits token forgery or session compromise.
The record
- CVE
- CVE-2025-15604
- Published
- Mar 28, 2026
- Updated
- Mar 28, 2026
- Vendor
- Tokuhiro Matsuno
- Product
- Amon2
- Classifications
- CWE-340, CWE-338, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 28, 2026CVE publishedPublication date reported by the CVE source.
- Mar 28, 2026Record 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 <6.17
What conditions does exploitation require?
What is affected?
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