Account activation via predictable security tokens
Published Aug 12, 2024 · Updated Aug 12, 2024
Insufficiently random activation tokens in FIWARE Keyrock 8.4 and earlier allow remote authenticated users to activate any new account. The activation-token generator derives security tokens from predictable Math.random() output, while the /activate route accepts a predicted token without authentication. A non-admin account must first request multiple password-reset tokens to recover the generator state; successful prediction changes an unactivated account to active.
Summary
What happened
Insufficiently random activation tokens in FIWARE Keyrock 8.4 and earlier allow remote authenticated users to activate any new account. The activation-token generator derives security tokens from predictable Math.random() output, while the /activate route accepts a predicted token without authentication. A non-admin account must first request multiple password-reset tokens to recover the generator state; successful prediction changes an unactivated account to active.
The record
- CVE
- CVE-2024-42165
- Published
- Aug 12, 2024
- Updated
- Aug 12, 2024
- Vendor
- FIWARE
- Product
- Keyrock
- Classifications
- CWE-330, CAPEC-59, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2024CVE publishedPublication date reported by the CVE source.
- Aug 12, 2024Record 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.4
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
- Activation-token prediction proof of conceptproof of concept · demonstrated
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