Session hijacking via predictable state identifiers
Published Sep 20, 2025 · Updated Sep 20, 2025
Predictable session identifiers in BLUEFEET Starch 0.01 through 0.14 allow remote attackers to access another user's session. Starch::Manager::state_id_seed concatenates a counter, time, Perl rand output, the PID, and reference addresses before SHA-1 hashing them. Exposure requires an application to use the default generated state ID as an authentication token; successful guessing grants only the victim session's application privileges.
Summary
What happened
Predictable session identifiers in BLUEFEET Starch 0.01 through 0.14 allow remote attackers to access another user's session. Starch::Manager::state_id_seed concatenates a counter, time, Perl rand output, the PID, and reference addresses before SHA-1 hashing them. Exposure requires an application to use the default generated state ID as an authentication token; successful guessing grants only the victim session's application privileges.
The record
- CVE
- CVE-2025-40925
- Published
- Sep 20, 2025
- Updated
- Sep 20, 2025
- Vendor
- BLUEFEET
- Product
- Starch
- Classifications
- CWE-338, CWE-340, CAPEC-115, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2025CVE publishedPublication date reported by the CVE source.
- Sep 20, 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.01 <=0.14
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