CVE-2023-45814

{"id": "CVE-2023-45814", "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 3.9}, {"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "published": "2023-10-18T22:15:09.497", "references": [{"url": "https://github.com/LittleBigRefresh/Bunkum/commit/6e109464ed9255f558182f001f475a378405ff76", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/LittleBigRefresh/Bunkum/security/advisories/GHSA-jrf2-h5j6-3rrq", "tags": ["Vendor Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-772"}]}, {"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-772"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Bunkum es un servidor de solicitudes independiente del protocolo de c\u00f3digo abierto para servidores de juegos personalizados. Primero, un poco de historia. Entonces, al principio, el \"AuthenticationService\" de Bunkum solo admit\u00eda la inyecci\u00f3n de \"IUser\". Sin embargo, a medida que Refresh y SoundShapesServer implementaron sistemas de permisos, se agreg\u00f3 soporte para inyectar \"IToken\" en los endpoints. Todo estuvo bien hasta el 4.0. Bunkum 4.0, luego cambi\u00f3 para imponer relaciones entre `IToken`s e `IUser`s. Esto no se implement\u00f3 de muy buena manera en `AuthenticationService` y termin\u00f3 rompiendo el almacenamiento en cach\u00e9 de tal manera que los tokens almacenados en cach\u00e9 persistir\u00edan despu\u00e9s de la vida \u00fatil de la solicitud, ya que intentamos almacenar en cach\u00e9 tanto los tokens como los usuarios. Desde ese momento hasta ahora, seg\u00fan tengo entendido, Bunkum estaba intentando usar ese token almacenado en cach\u00e9 al comienzo de la siguiente solicitud una vez almacenado en cach\u00e9. Naturalmente, cuando ese token expir\u00f3, los proyectos posteriores como Refresh eliminar\u00edan el objeto de Realm y provocar\u00edan que el objeto en el cach\u00e9 estuviera en un estado separado, lo que provocar\u00eda una excepci\u00f3n por el uso no v\u00e1lido de `IToken.User`. En otras palabras, un use-after-free ya que Realm no puede administrar la vida \u00fatil del token almacenado en cach\u00e9. En cuanto a la seguridad, el alcance es bastante limitado, solo se puede implementar en un par de endpoints dadas algunas condiciones y no se puede garantizar qu\u00e9 token obtendr\u00e1. Adem\u00e1s, el token *would* invalidar\u00eda correctamente si el endpoint tuviera un uso de \"IToken\" o un uso de \"IUser\". La soluci\u00f3n es simplemente borrar el cach\u00e9 del token despu\u00e9s de que se manej\u00f3 la solicitud, que ahora est\u00e1 en `4.2.1`. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad."}], "lastModified": "2023-10-30T17:16:15.390", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:littlebigfresh:bunkum:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "F4F0D6F2-C400-42D2-BFC4-908EC8742FDA", "versionEndExcluding": "4.2.1", "versionStartIncluding": "4.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}