Session hijacking via insecure legacy cookies
Published Mar 16, 2022 · Updated Aug 3, 2024
Cleartext cookie transmission in Gradle Enterprise 2020.1 through 2021.4.2 enables attackers to capture authenticated sessions. Keycloak sets duplicate legacy cookies ending in _LEGACY without the Secure attribute; browsers transmit the cookies over plain HTTP. Exploitation requires host impersonation and an authenticated victim clicking an HTTP link, resulting in capture of the victim's login session.
Summary
What happened
Cleartext cookie transmission in Gradle Enterprise 2020.1 through 2021.4.2 enables attackers to capture authenticated sessions. Keycloak sets duplicate legacy cookies ending in _LEGACY without the Secure attribute; browsers transmit the cookies over plain HTTP. Exploitation requires host impersonation and an authenticated victim clicking an HTTP link, resulting in capture of the victim's login session.
The record
- CVE
- CVE-2022-27225
- Published
- Mar 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-311, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
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