# CVE-2019-1010258: Memory corruption in nanosvg

> A buffer overflow in the nanosvg library allows attackers to cause memory corruption and denial of service via crafted SVG files.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mw69-v2cv-29ww

## What is CVE-2019-1010258?

CVE-2019-1010258 is a medium-severity memory corruption vulnerability in nanosvg, published on 15 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

nanosvg library nanosvg after commit c1f6e209c16b18b46aa9f45d7e619acf42c29726 is affected by: Buffer Overflow. The impact is: Memory corruption leading to at least DoS. More severe impact vectors need more investigation. The component is: it's part of a svg processing library. function nsvg__parseColorRGB in src/nanosvg.h / line 1227. The attack vector is: It depends library usage. If input is passed from the network, then network connectivity is enough. Most likely an attack will require opening a specially crafted .svg file.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-1010258?

It affects 1 product.


Products: Nanosvg Project Nanosvg.

## How do I fix CVE-2019-1010258?

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

## Is CVE-2019-1010258 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1010258 and fix it if it is affected.

What it is: CVE-2019-1010258 is a medium-severity memory corruption vulnerability in nanosvg, published on 15 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-1010258 in the wild and no public exploit code.

Affected product: nanosvg. 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-2019-1010258/ (Markdown: https://insights.sbomify.com/CVE-2019-1010258/index.md)
```

## Sources

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

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