Akeo Consulting Rufus fails to securely check for and retrieve updates, which an allow an authenticated attacker to execute arbitrary code on a vulnerable system.
Akeo Consulting Rufus 2.16 retrieves updates over HTTP. While Rufus does attempt to perform some basic signature checking of downloaded updates, it does not ensure that the update was signed by a trusted certificate authority (CA). This lack of CA checking allows the use of a self-signed certificate. Because of these two weaknesses, an attacker can subvert the update process to achieve arbitrary code execution.
An attacker on the same network as, or who can otherwise affect network traffic from, a Rufus user can cause the Rufus update process to execute arbitrary code.
Apply an update
This issue is addressed in Rufus 2.17.1187. Please also consider the following workarounds:
Don't use built-in update capabilities
This issue was reported by Will Dormann of the CERT/CC.
This document was written by Will Dormann.
|Date First Published:||2017-08-29|
|Date Last Updated:||2017-08-31 14:58 UTC|