# CVE-2017-7869: Memory corruption in n/a

> An out-of-bounds write in GnuTLS allows attackers to execute arbitrary code or cause denial of service via crafted packets.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 14 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-7869, GHSA-8cj2-6v9c-5x8f, UBUNTU-CVE-2017-7869

## What is CVE-2017-7869?

CVE-2017-7869 is a high-severity memory corruption vulnerability in Gnu Gnutls, published on 14 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GnuTLS before 2017-02-20 has an out-of-bounds write caused by an integer overflow and heap-based buffer overflow related to the cdk_pkt_read function in opencdk/read-packet.c. This issue (which is a subset of the vendor's GNUTLS-SA-2017-3 report) is fixed in 3.5.10.

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

## Which versions are affected by CVE-2017-7869?

It affects 1 product.


Products: Gnu Gnutls.

## How do I fix CVE-2017-7869?

Upgrade to a fixed version.

## Is CVE-2017-7869 being exploited?

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

## Other vulnerabilities in Gnu Gnutls

- [CVE-2008-1948](https://insights.sbomify.com/CVE-2008-1948/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-5334](https://insights.sbomify.com/CVE-2017-5334/): Use after free in n/a (critical 9.8)
- [CVE-2017-5336](https://insights.sbomify.com/CVE-2017-5336/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-5337](https://insights.sbomify.com/CVE-2017-5337/): Memory corruption in n/a (critical 9.8)
- [CVE-2008-1949](https://insights.sbomify.com/CVE-2008-1949/): Null dereference in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7869 and fix it if it is affected.

What it is: CVE-2017-7869 is a high-severity memory corruption vulnerability in Gnu Gnutls, published on 14 Apr 2017. 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-2017-7869 in the wild and no public exploit code.

Affected product: Gnu Gnutls. 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-2017-7869/ (Markdown: https://insights.sbomify.com/CVE-2017-7869/index.md)
```

## Sources

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

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