# CVE-2018-1000517: Memory corruption in n/a

> A heap buffer overflow in BusyBox wget allows remote attackers to execute arbitrary code or cause a denial of service via network connectivity.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Jun 2018
- **Updated:** 9 Jun 2025
- **Also known as:** DEBIAN-CVE-2018-1000517, GHSA-m9j3-9rqj-pg6p, UBUNTU-CVE-2018-1000517

## What is CVE-2018-1000517?

CVE-2018-1000517 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 26 Jun 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

BusyBox project BusyBox wget version prior to commit 8e2174e9bd836e53c8b9c6e00d1bc6e2a718686e contains a Buffer Overflow vulnerability in Busybox wget that can result in heap buffer overflow. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in after commit 8e2174e9bd836e53c8b9c6e00d1bc6e2a718686e.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2018-1000517?

It affects 3 products.


Products: Busybox Busybox, Canonical Ubuntu Linux, Debian Debian Linux.

## How do I fix CVE-2018-1000517?

Apply the vendor's patch.

## Is CVE-2018-1000517 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2022-48174](https://insights.sbomify.com/CVE-2022-48174/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-42377](https://insights.sbomify.com/CVE-2021-42377/): Memory corruption in busybox (critical 9.8)
- [CVE-2016-2148](https://insights.sbomify.com/CVE-2016-2148/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-28391](https://insights.sbomify.com/CVE-2022-28391/): Command injection in n/a (high 8.8)
- [CVE-2017-16544](https://insights.sbomify.com/CVE-2017-16544/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000517 and fix it if it is affected.

What it is: CVE-2018-1000517 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 26 Jun 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1000517 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2018-1000517/ (Markdown: https://insights.sbomify.com/CVE-2018-1000517/index.md)
```

## Sources

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

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