CVE-2017-6466

UnknownEPSS 1.54%

Last modified

CVE-2017-6466 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.54% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
1.54%

71.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
F-SecureSoftware Updater2.20

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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 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.
How severe is CVE-2017-6466?
Severity scoring for CVE-2017-6466 is pending analysis. The EPSS model estimates a 1.54% probability of exploitation in the next 30 days.
How do I fix CVE-2017-6466?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-6466?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST