Token disclosure via stale AuthenticationService cache reuse
Published Oct 18, 2023 · Updated Sep 13, 2024
Use-after-free in Bunkum 4.0.0 through 4.2.0 allows remote attackers to access another user's token through crafted request sequences. The AuthenticationService retains its per-request IToken cache after a request ends, then dereferences IToken.User after Realm detaches an expired token. Triggering requires authenticated requests against limited endpoints that do not consume IToken or IUser, and the selected stale token is unpredictable.
Summary
What happened
Use-after-free in Bunkum 4.0.0 through 4.2.0 allows remote attackers to access another user's token through crafted request sequences. The AuthenticationService retains its per-request IToken cache after a request ends, then dereferences IToken.User after Realm detaches an expired token. Triggering requires authenticated requests against limited endpoints that do not consume IToken or IUser, and the selected stale token is unpredictable.
The record
- CVE
- CVE-2023-45814
- Published
- Oct 18, 2023
- Updated
- Sep 13, 2024
- Vendor
- PlanetBunkum
- Product
- Bunkum
- Classifications
- CWE-772, CAPEC-469
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 18, 2023CVE publishedPublication date reported by the CVE source.
- Sep 13, 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=>= 4.0.0, < 4.2.1
- Affected versionversion=4.0.0 <4.2.1
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