# CVE-2018-1000500: Security feature bypass in n/a

> BusyBox wget fails to validate SSL certificates, allowing attackers to execute arbitrary code via man-in-the-middle attacks on HTTPS downloads.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jun 2018
- **Updated:** 9 Jun 2025
- **Also known as:** ALPINE-CVE-2018-1000500, DEBIAN-CVE-2018-1000500, ECHO-76f9-203f-42fd, GHSA-248x-4c3j-hcg7, MGASA-2021-0009, UBUNTU-CVE-2018-1000500, USN-4531-1

## What is CVE-2018-1000500?

CVE-2018-1000500 is a medium-severity vulnerability in n/a, published on 26 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Busybox contains a Missing SSL certificate validation vulnerability in The "busybox wget" applet that can result in arbitrary code execution. This attack appear to be exploitable via Simply download any file over HTTPS using "busybox wget https://compromised-domain.com/important-file".

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Busybox Busybox.

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

Apply the vendor's patch.

## Is CVE-2018-1000500 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1000500 exists.

## Other vulnerabilities in n/a

- [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-1000500 and fix it if it is affected.

What it is: CVE-2018-1000500 is a medium-severity vulnerability in n/a, published on 26 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1000500 exists.

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

## Sources

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

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