{"vulnerability": "CVE-2024-41942", "sightings": [{"uuid": "811bb43a-d724-4e06-b5b6-e591488de264", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41942", "type": "seen", "source": "https://t.me/cvedetector/2796", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41942 - JupyterHub Privilege Escalation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-41942 \nPublished : Aug. 8, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : JupyterHub is software that allows one to create a multi-user server for Jupyter notebooks. Prior to versions 4.1.6 and 5.1.0, if a user is granted the `admin:users` scope, they may escalate their own privileges by making themselves a full admin user. The impact is relatively small in that `admin:users` is already an extremely privileged scope only granted to trusted users.  \nIn effect, `admin:users` is equivalent to `admin=True`, which is not intended. Note that the change here only prevents escalation to the built-in JupyterHub admin role that has unrestricted permissions. It does not prevent users with e.g. `groups` permissions from granting themselves or other users permissions via group membership, which is intentional. Versions 4.1.6 and 5.1.0 fix this issue. \nSeverity: 7.2 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-08T18:04:36.000000Z"}]}