# CVE-2017-6466: Code injection in n/a

> Man-in-the-middle attackers can replace downloaded updates with malicious executables, leading to code execution with SYSTEM privileges.

- **Severity:** High 8.1 (`CVSS:3.0/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:** No
- **Published:** 11 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5vww-3gh7-86vf

## What is CVE-2017-6466?

CVE-2017-6466 is a high-severity code injection vulnerability in n/a, published on 11 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

F-Secure Software Updater 2.20, as distributed in several F-Secure products, downloads installation packages over plain http and does not perform file integrity validation after download. Man-in-the-middle attackers can replace the file with their own executable which will be executed under the SYSTEM account. Note that when Software Updater is configured to install updates automatically, it checks if the downloaded file is digitally signed by default, but does not check the author of the signature. When running in manual mode (default), no signature check is performed.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: F-Secure Software Updater.

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

No fix has been published for CVE-2017-6466 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-6466 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6466 is a high-severity code injection vulnerability in n/a, published on 11 Mar 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-6466 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-6466/ (Markdown: https://insights.sbomify.com/CVE-2017-6466/index.md)
```

## Sources

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

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