# CVE-2019-19005: Use after free in n/a

> Attackers can trigger a double free vulnerability in autotrace via malformed bitmap images, potentially leading to code execution or denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Feb 2021
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h25v-w22w-w3pj, UBUNTU-CVE-2019-19005

## What is CVE-2019-19005?

CVE-2019-19005 is a high-severity use after free vulnerability in Autotrace Project Autotrace, published on 11 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A bitmap double free in main.c in autotrace 0.31.1 allows attackers to cause an unspecified impact via a malformed bitmap image. This may occur after the use-after-free in CVE-2017-9182.

Weakness: CWE-415 (Double Free)

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

It affects 2 products.


Products: Autotrace Project Autotrace, Fedoraproject Fedora.

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

Apply the vendor's patch.

## Is CVE-2019-19005 being exploited?

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

## Other vulnerabilities in Autotrace Project Autotrace

- [CVE-2017-9151](https://insights.sbomify.com/CVE-2017-9151/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9152](https://insights.sbomify.com/CVE-2017-9152/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9153](https://insights.sbomify.com/CVE-2017-9153/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9160](https://insights.sbomify.com/CVE-2017-9160/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9161](https://insights.sbomify.com/CVE-2017-9161/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19005 is a high-severity use after free vulnerability in Autotrace Project Autotrace, published on 11 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-19005 in the wild and no public exploit code.

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

## Sources

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

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