Session reuse via persistent browser-close cookies
Published Apr 5, 2023 · Updated Feb 10, 2025
Insufficient session expiration in Firefly III before 6.0.0 allows remote authenticated users to reuse sessions after browser closure. The session configuration sets expire_on_close to false, so closing the browser leaves the session cookie valid instead of expiring it. Exploitation requires possession of a previously valid session cookie and preserves access to the associated account after the browser closes.
Summary
What happened
Insufficient session expiration in Firefly III before 6.0.0 allows remote authenticated users to reuse sessions after browser closure. The session configuration sets expire_on_close to false, so closing the browser leaves the session cookie valid instead of expiring it. Exploitation requires possession of a previously valid session cookie and preserves access to the associated account after the browser closes.
The record
- CVE
- CVE-2023-1788
- Published
- Apr 5, 2023
- Updated
- Feb 10, 2025
- Vendor
- Firefly III
- Product
- Firefly III
- Classifications
- CWE-613, T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 5, 2023CVE publishedPublication date reported by the CVE source.
- Feb 10, 2025Record 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=unspecified <6
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