# CVE-2017-18641: Supply chain in n/a

> Attackers can inject malicious code into LXC containers by intercepting unverified HTTP downloads during template bootstrapping.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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:** 10 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-18641, GHSA-rv6g-hrqv-7f3p, UBUNTU-CVE-2017-18641

## What is CVE-2017-18641?

CVE-2017-18641 is a high-severity vulnerability in n/a, published on 10 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In LXC 2.0, many template scripts download code over cleartext HTTP, and omit a digital-signature check, before running it to bootstrap containers.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Linuxcontainers Lxc.

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

Apply the vendor's patch.

## Is CVE-2017-18641 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-8649](https://insights.sbomify.com/CVE-2016-8649/): Path traversal in LXC before 1.0.9 and 2.x before 2.0.6 (critical 9.1)
- [CVE-2016-10124](https://insights.sbomify.com/CVE-2016-10124/): Privilege escalation in n/a (high 8.6)
- [CVE-2013-6441](https://insights.sbomify.com/CVE-2013-6441/): Privilege escalation in n/a (high 7.2)
- [CVE-2015-1331](https://insights.sbomify.com/CVE-2015-1331/): Path traversal in n/a (medium 4.9)
- [CVE-2015-1334](https://insights.sbomify.com/CVE-2015-1334/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18641 is a high-severity vulnerability in n/a, published on 10 Feb 2020. 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-18641 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-2017-18641/ (Markdown: https://insights.sbomify.com/CVE-2017-18641/index.md)
```

## Sources

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

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