CVE-2017-18641 Supply chain in n/a
High 8.1
Published
Updated
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)
Attackers can inject malicious code into LXC containers by intercepting unverified HTTP downloads during template bootstrapping.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
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
Which versions are affected by CVE-2017-18641?
It affects 1 product.
Products include 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
Sources
Also known as DEBIAN-CVE-2017-18641, GHSA-rv6g-hrqv-7f3p, UBUNTU-CVE-2017-18641.