CVE-2023-45814

Bunkum is an open-source protocol-agnostic request server for custom game servers. First, a little bit of background. So, in the beginning, Bunkum's `AuthenticationService` only supported injecting `IUser`s. However, as Refresh and SoundShapesServer implemented permissions systems support for injecting `IToken`s into endpoints was added. All was well until 4.0. Bunkum 4.0 then changed to enforce relations between `IToken`s and `IUser`s. This wasn't implemented in a very good way in the `AuthenticationService`, and ended up breaking caching in such a way that cached tokens would persist after the lifetime of the request - since we tried to cache both tokens and users. From that point until now, from what I understand, Bunkum was attempting to use that cached token at the start of the next request once cached. Naturally, when that token expired, downstream projects like Refresh would remove the object from Realm - and cause the object in the cache to be in a detached state, causing an exception from invalid use of `IToken.User`. So in other words, a use-after-free since Realm can't manage the lifetime of the cached token. Security-wise, the scope is fairly limited, can only be pulled off on a couple endpoints given a few conditions, and you can't guarantee which token you're going to get. Also, the token *would* get invalidated properly if the endpoint had either a `IToken` usage or a `IUser` usage. The fix is to just wipe the token cache after the request was handled, which is now in `4.2.1`. Users are advised to upgrade. There are no known workarounds for this vulnerability.

• CWE-772
• CWE-772

• https://github.com/LittleBigRefresh/Bunkum/commit/6e109464ed9255f558182f001f475a378405ff76Patch
• https://github.com/LittleBigRefresh/Bunkum/security/advisories/GHSA-jrf2-h5j6-3rrqVendor Advisory
• https://github.com/LittleBigRefresh/Bunkum/commit/6e109464ed9255f558182f001f475a378405ff76Patch
• https://github.com/LittleBigRefresh/Bunkum/security/advisories/GHSA-jrf2-h5j6-3rrqVendor Advisory

Published

Oct 18, 2023

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2023-45809Wagtail is an open source content management system built on…2.7
• CVE-2023-4581Excel `.xll` add-in files did not have a blocklist entry in …4.3
• CVE-2023-45810OpenFGA is a flexible authorization/permission engine built …7.5
• CVE-2023-45811Synchrony deobfuscator is a javascript cleaner & deobfuscato…7.8
• CVE-2023-45812The Apollo Router is a configurable, high-performance graph …7.5
• CVE-2023-45813Torbot is an open source tor network intelligence tool. In a…7.5
• CVE-2023-45815ArchiveBox is an open source self-hosted web archiving syste…5.4
• CVE-2023-45816Discourse is an open source platform for community discussio…3.3
• CVE-2023-45817Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
• CVE-2023-45818TinyMCE is an open source rich text editor. A mutation cross…6.1
• CVE-2023-45819TinyMCE is an open source rich text editor. A cross-site scr…6.1
• CVE-2023-4582Due to large allocation checks in Angle for glsl shaders bei…8.8