Unauthenticated account takeover via trusted user cookie
Published Nov 20, 2023 · Updated Aug 2, 2024
Authorization bypass in Dev Blog 1.0 allows remote attackers to take over any user's account through a crafted user cookie. Its request authentication logic treats the attacker-controlled user cookie as the account lookup key without binding that value to an authenticated server-side session. Knowledge of a target username is the only reported gate, and successful exploitation exposes that user's session and permits actions with the victim's account privileges.
Summary
What happened
Authorization bypass in Dev Blog 1.0 allows remote attackers to take over any user's account through a crafted user cookie. Its request authentication logic treats the attacker-controlled user cookie as the account lookup key without binding that value to an authenticated server-side session. Knowledge of a target username is the only reported gate, and successful exploitation exposes that user's session and permits actions with the victim's account privileges.
The record
- CVE
- CVE-2023-6144
- Published
- Nov 20, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-639, CAPEC-153, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 20, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
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
- Fluid Attacks account-takeover demonstrationproof 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