# CVE-2023-24288: Denial of service in Portable Puzzle Collection

> Attackers can cause a Denial of Service in Portable Puzzle Collection by creating an excessive number of save states.

- **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-24288, GHSA-vcxx-58r4-45w9, UBUNTU-CVE-2023-24288

## What is CVE-2023-24288?

CVE-2023-24288 is a low-severity denial of service 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

An issue in Portable Puzzle Collection before 20230116.5782e29 allows attackers to cause a Denial of Service (DoS) via creating an excessive amount of save states.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Upgrade to a fixed version.

## Is CVE-2023-24288 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-24288 is a low-severity denial of service 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-24288 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-24288/ (Markdown: https://insights.sbomify.com/CVE-2023-24288/index.md)
```

## Sources

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

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