# CVE-2023-44709: Integer overflow in n/a

> An integer overflow in PlutoSVG's memory loading function can lead to denial of service, affecting applications using this library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Dec 2023
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-pwjh-vjhv-xqmx

## What is CVE-2023-44709?

CVE-2023-44709 is a critical vulnerability in n/a, published on 14 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PlutoSVG commit 336c02997277a1888e6ccbbbe674551a0582e5c4 and before was discovered to contain an integer overflow via the component plutosvg_load_from_memory.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Sammycage Plutosvg.

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

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

## Is CVE-2023-44709 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-44709 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-44709 is a critical vulnerability in n/a, published on 14 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-44709 exists.

Affected product: n/a. 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-44709/ (Markdown: https://insights.sbomify.com/CVE-2023-44709/index.md)
```

## Sources

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

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