Cohen's post described the vulnerability as remote code execution flaw. However, physical access is a prerequisite
An AMD spokesperson told The Register that an attacker would first have to gain access to the motherboard and then modify SPI-Flash before the issue could be exploited
> Cohen's post described the vulnerability as remote code execution flaw. However, physical access is a prerequisite
>An AMD spokesperson told The Register that an attacker would first have to gain access to the motherboard and then modify SPI-Flash before the issue could be exploited
The problem is that you can't know if AME is still running on the first network interface if you won't plug it on the dedicated one. Even if you disable it.
Also "physical" is relative, remote KVM is standard now.
The problem is that you can't know if AME is still running on the first network interface if you won't plug it on the dedicated one. Even if you disable it.
Also "physical" is relative, remote KVM is standard now.
4 comments
The problem is that you can't know if AME is still running on the first network interface if you won't plug it on the dedicated one. Even if you disable it.
Also "physical" is relative, remote KVM is standard now.
What is remote KVM?
Remote access to Keyboard, Video and Mouse. Basically remote access to a system even before it has booted.