Session hijacking via logout token retention
Published Feb 17, 2024 · Updated Dec 6, 2024
Insufficient session expiration in all versions of Greenpau Caddy Security allows attackers to reuse logged-out sessions. The /logout and /oauth2/google/logout handlers complete sign-out without invalidating the associated session token, so the token remains accepted. Exploitation requires access to a previously active user session and grants the same application actions that the session owner could perform.
Summary
What happened
Insufficient session expiration in all versions of Greenpau Caddy Security allows attackers to reuse logged-out sessions. The /logout and /oauth2/google/logout handlers complete sign-out without invalidating the associated session token, so the token remains accepted. Exploitation requires access to a previously active user session and grants the same application actions that the session owner could perform.
The record
- CVE
- CVE-2024-21492
- Published
- Feb 17, 2024
- Updated
- Dec 6, 2024
- Vendor
- Greenpau
- Product
- Caddy Security
- Classifications
- CWE-613, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 2024CVE publishedPublication date reported by the CVE source.
- Dec 6, 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 <*
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
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