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

> A double-free vulnerability in GNU Recutils allows attackers to cause denial of service or potentially execute arbitrary code.

- **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:** Yes
- **Published:** 16 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-6455, GHSA-pjj8-r5h4-4q77, UBUNTU-CVE-2019-6455

## What is CVE-2019-6455?

CVE-2019-6455 is a medium-severity use after free vulnerability in n/a, published on 16 Jan 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

An issue was discovered in GNU Recutils 1.8. There is a double-free problem in the function rec_mset_elem_destroy() in the file rec-mset.c.

Weakness: CWE-415 (Double Free)

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

It affects 1 product.


Products: Gnu Recutils.

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

Upgrade to a fixed version.

## Is CVE-2019-6455 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-11639](https://insights.sbomify.com/CVE-2019-11639/): Memory corruption in n/a (high 8.8)
- [CVE-2019-11640](https://insights.sbomify.com/CVE-2019-11640/): Memory corruption in n/a (high 8.8)
- [CVE-2025-65409](https://insights.sbomify.com/CVE-2025-65409/): Denial of service in n/a (high 7.5)
- [CVE-2019-11637](https://insights.sbomify.com/CVE-2019-11637/): Null dereference in n/a (medium 6.5)
- [CVE-2019-11638](https://insights.sbomify.com/CVE-2019-11638/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6455 is a medium-severity use after free vulnerability in n/a, published on 16 Jan 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-6455 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-6455/ (Markdown: https://insights.sbomify.com/CVE-2019-6455/index.md)
```

## Sources

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

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