Account takeover via persistent post-logout session cookie
Published Mar 7, 2021 · Updated Aug 7, 2024
Insufficient session expiration in MantisBT before 2.24.5 allows remote attackers with a captured cookie to access a user's account. The auth_logout() function clears browser and cached state but leaves the database-backed cookie_string unchanged and valid. Possession of a previously issued user cookie is required, and replay after that user logs out restores that user's application privileges.
Summary
What happened
Insufficient session expiration in MantisBT before 2.24.5 allows remote attackers with a captured cookie to access a user's account. The auth_logout() function clears browser and cached state but leaves the database-backed cookie_string unchanged and valid. Possession of a previously issued user cookie is required, and replay after that user logs out restores that user's application privileges.
The record
- CVE
- CVE-2009-20001
- Published
- Mar 7, 2021
- Updated
- Aug 7, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-613, T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 7, 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.
Public exploit references
- Post-logout cookie replay demonstrationfunctional · validated
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