# CVE-2022-24781: Malicious users can take over the session of other players

> Attackers can hijack other players' sessions by spoofing UUIDs, allowing unauthorized access to game sessions.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-4fv9-g2jh-j5xm

## What is CVE-2022-24781?

CVE-2022-24781 is a high-severity authentication bypass vulnerability in math-geon Geon, published on 24 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Geon is a board game based on solving questions about the Pythagorean Theorem. Malicious users can obtain the uuid from other users, spoof that uuid through the browser console and become co-owners of the target session. This issue is patched in version 1.1.0. No known workaround exists.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2022-24781?

It affects 1 product.


Products: Geon Project Geon.

## How do I fix CVE-2022-24781?

No fix has been published for CVE-2022-24781 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-24781 being exploited?

There is no known exploitation of CVE-2022-24781 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24781 and fix it if it is affected.

What it is: CVE-2022-24781 is a high-severity authentication bypass vulnerability in math-geon Geon, published on 24 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24781 in the wild and no public exploit code.

Affected product: math-geon Geon. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24781/ (Markdown: https://insights.sbomify.com/CVE-2022-24781/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24781
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24781
- OSV: https://osv.dev/vulnerability/CVE-2022-24781

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24781/
Summaries are generated and may contain mistakes; the official description above is the record.