# CVE-2023-24286: Memory corruption in Portable Puzzle Collection

> A buffer overflow in Portable Puzzle Collection allows attackers to execute arbitrary code or cause denial of service via a crafted game description.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** DEBIAN-CVE-2023-24286, GHSA-64jv-qcg3-4pjj, UBUNTU-CVE-2023-24286

## What is CVE-2023-24286?

CVE-2023-24286 is a low-severity memory corruption vulnerability in Simon Tatham Portable Puzzle Collection, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Portable Puzzle Collection before 20230116.5782e29 was discovered to contain a buffer overflow via the game description parameter.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2023-24286?


## How do I fix CVE-2023-24286?

Upgrade to a fixed version.

## Is CVE-2023-24286 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24286 and fix it if it is affected.

What it is: CVE-2023-24286 is a low-severity memory corruption vulnerability in Simon Tatham Portable Puzzle Collection, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-24286 in the wild and no public exploit code.

Affected product: Simon Tatham Portable Puzzle Collection. 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-2023-24286/ (Markdown: https://insights.sbomify.com/CVE-2023-24286/index.md)
```

## Sources

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

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