Victim action hijacking via cookie tossing
Published Jul 19, 2024 · Updated Oct 31, 2024
Cookie tossing in Gitpod Classic before main-gha.27122 allows remote authenticated users to bind victim actions to an attacker session. CookieNameFromDomain generated a domain-scoped gitpod_io_jwt2 cookie without the __Host- prefix, allowing a controlled subdomain to overwrite it. Exploitation requires subdomain control and victim interaction, causing selected victim operations, such as connecting a GitHub organization, to execute in the attacker's session.
Summary
What happened
Cookie tossing in Gitpod Classic before main-gha.27122 allows remote authenticated users to bind victim actions to an attacker session. CookieNameFromDomain generated a domain-scoped gitpod_io_jwt2 cookie without the __Host- prefix, allowing a controlled subdomain to overwrite it. Exploitation requires subdomain control and victim interaction, causing selected victim operations, such as connecting a GitHub organization, to execute in the attacker's session.
The record
- CVE
- CVE-2024-21583
- Published
- Jul 19, 2024
- Updated
- Oct 31, 2024
- Vendor
- Gitpod
- Product
- Gitpod Classic
- Classifications
- CWE-565, CWE-15, T1185
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2024CVE publishedPublication date reported by the CVE source.
- Oct 31, 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 <0.1.5-main-gha.27122
- Affected versionversion=0 <main-gha.27122
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