Session hijacking via namespace-blind cache invalidation
Published Sep 18, 2023 · Updated Sep 24, 2024
Session expiration failure in Pow 1.0.14 through 1.0.33 allows remote authenticated users to hijack sessions through stale cache keys. The startup table fold strips each stored key's namespace through unwrap(), then schedules expiration under the default namespace instead of its stored namespace. Exploitation requires the Mnesia backend, possession of a previously issued session, and shutdown of every cache instance for longer than that session's remaining lifetime.
Summary
What happened
Session expiration failure in Pow 1.0.14 through 1.0.33 allows remote authenticated users to hijack sessions through stale cache keys. The startup table fold strips each stored key's namespace through unwrap(), then schedules expiration under the default namespace instead of its stored namespace. Exploitation requires the Mnesia backend, possession of a previously issued session, and shutdown of every cache instance for longer than that session's remaining lifetime.
The record
- CVE
- CVE-2023-42446
- Published
- Sep 18, 2023
- Updated
- Sep 24, 2024
- Vendor
- Pow Auth
- Product
- Pow
- Classifications
- CWE-298, CWE-672, T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 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=>= 1.0.14, < 1.0.34
What conditions does exploitation require?
What is affected?
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.
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