# CVE-2019-6246: Memory corruption in n/a

> An out-of-bounds read in SVG++ can cause an access violation and crash the application when processing specific SVG images.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** Yes
- **Published:** 13 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2019-6246, GHSA-p32g-q42f-c4jr, UBUNTU-CVE-2019-6246

## What is CVE-2019-6246?

CVE-2019-6246 is a critical memory corruption vulnerability in n/a, published on 13 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in SVG++ (aka svgpp) 1.2.3. After calling the gil::get_color function in Generic Image Library in Boost, the return code is used as an address, leading to an Access Violation because of an out-of-bounds read.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Svgpp Svgpp.

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

Upgrade to a fixed version.

## Is CVE-2019-6246 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-44960](https://insights.sbomify.com/CVE-2021-44960/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6246 is a critical memory corruption vulnerability in n/a, published on 13 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6246 in the wild and no public exploit code.

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

## Sources

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

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