logoalt Hacker News

ano-theryesterday at 10:57 AM3 repliesview on HN

Not that this isn’t bad, doesn’t this only apply when an update is available?

So you have to be on a shady hotspot, without VPN, AMD has recently published an update, and your update scheduler is timed to run.

That would be a little less than “immediately own anyone with ATI”.


Replies

Gindenyesterday at 1:18 PM

You need only a device on network to spam DHCP messages with malware DNS. So you don't need "shady hotspot", only compromised device within network.

rtpgyesterday at 8:14 PM

Oh yeah fair point, the HTTPS-ness of the first step is a helpful backstop

pmontrayesterday at 12:12 PM

If somebody is MITMing a target person, they will respond positively to "update available?" calls from that person and then serve the tainted update. The article does not say what the frequency of auto update check is. Let's say one per day. If somebody is targeted it's one day away from RCE.

show 1 reply