Continued account access via reusable logged-out JWT
Published Apr 16, 2024 · Updated Aug 1, 2024
Session fixation in ZenML before 0.56.2 allows remote attackers to retain account access by replaying a victim's logged-out JWT. The logout flow does not invalidate the signed JWT, so later requests bearing the token remain authenticated. Exploitation requires acquisition of a victim's token and user interaction with logout; successful reuse permits access and actions within that account.
Summary
What happened
Session fixation in ZenML before 0.56.2 allows remote attackers to retain account access by replaying a victim's logged-out JWT. The logout flow does not invalidate the signed JWT, so later requests bearing the token remain authenticated. Exploitation requires acquisition of a victim's token and user interaction with logout; successful reuse permits access and actions within that account.
The record
- CVE
- CVE-2024-2260
- Published
- Apr 16, 2024
- Updated
- Aug 1, 2024
- Vendor
- ZenML
- Product
- ZenML
- Classifications
- CWE-384, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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.56.2
- Affected versionversion=unspecified <0.56.2
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.
Public exploit references
- huntr.dev JWT reuse bounty reportproof of concept · unverified
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