Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

AMD plugs firmware holes that allowed command injection

Bug your motherboard vendor for a fix, says boffin

VID Chip maker AMD has patched holes across its firmware lines that could allow hackers to inject malware.

Czech programmer Rudolf Marek reported the holes in the Trinity, Richland, Kaveri, and Kabini silicon series ahead of a disclosure at the Chaos Communications Congress.

AMD's System Management Unit (SMU) firmware code within x86 processors did not run adequate checks prior to execution, allowing Marek to inject his own commands.

Marek told attendees to ask their mainboard vendors to push the fixed AGESA to BIOSes.

"Tell your vendors for a fixed AGESA (AMD Generic Encapsulated Software Architecture)," Marek said during the talk aimed at encouraging more of the low-level security analysis.

"This is the only way to push vendors to update BIOSes for older platforms."

Marek did not describe particular attack scenarios created by the lack of a protected code along with further firmware errors.

It took roughly a year to fix the flaws in an exchange he described as "responsible and helpful".

®

 

Similar topics

Similar topics

Similar topics

TIP US OFF

Send us news


Other stories you might like