Researchers discover potentially catastrophic exploit present in AMD chips
Researchers have found a serious vulnerability in AMD processors, affecting chips since 2006, allowing deep firmware access. AMD is developing patches, with risks primarily for corporations and government entities.
Read original articleResearchers from IOActive have identified a significant vulnerability in AMD processors, termed the "Sinkclose" flaw, which has existed for over a decade. This security issue resides in the firmware of AMD chips, potentially allowing malware to gain deep access to a computer's memory and execute code in the System Management Mode, a highly privileged area of the processor. The flaw affects nearly all AMD chips dating back to at least 2006. While the exploit is serious, it is unlikely to impact average users, as attackers would need extensive access to the system to exploit it fully. However, the risk is heightened for corporations and government entities, as the malicious code could remain undetected even after an operating system reinstall. AMD has acknowledged the vulnerability and is working on mitigation strategies for affected products, although the company emphasizes that exploiting this flaw requires overcoming significant security measures. IOActive has refrained from releasing proof-of-concept code while AMD develops patches, stressing the urgency of addressing the issue to maintain overall system security.
- A significant vulnerability in AMD processors has been discovered, affecting nearly all chips since 2006.
- The exploit allows deep access to a computer's firmware, posing risks primarily to corporations and government entities.
- AMD is working on mitigation strategies and has acknowledged the seriousness of the flaw.
- Exploiting the vulnerability requires extensive access, making it less likely to affect average users.
- IOActive has chosen not to publish proof-of-concept code while AMD develops necessary patches.
Related
Vulnerability in Popular PC and Server Firmware
Eclypsium found a critical vulnerability (CVE-2024-0762) in Intel Core processors' Phoenix SecureCore UEFI firmware, potentially enabling privilege escalation and persistent attacks. Lenovo issued BIOS updates, emphasizing the significance of supply chain security.
Secure Boot is completely broken on 200 models from 5 big device makers
Researchers from Binarly found that Secure Boot is compromised on over 200 device models due to a leaked cryptographic key, posing significant security risks until manufacturers issue firmware updates.
Compromising the Secure Boot Process
Researchers from Binarly revealed a security vulnerability in the Secure Boot process affecting over 200 device models due to a leaked cryptographic key, raising concerns about potential cyberattacks and security practices.
Secure Boot useless on PCs from major vendors after key leak
A study by Binarily found that hundreds of PCs from major manufacturers are vulnerable due to a leaked 12-year-old test platform key, allowing attackers to bypass Secure Boot protections.
New SLUBStick Attack Makes Linux Kernel Vulnerabilities More Dangerous
Researchers from Graz University of Technology developed SLUBStick, a technique that exploits Linux kernel heap vulnerabilities with over 99% success, enabling privilege escalation and container escapes against modern defenses.
> Improper validation in a model specific register (MSR) could allow a malicious program with ring0 access to modify SMM configuration while SMI lock is enabled, potentially leading to arbitrary code execution.
So that’s pretty bad. Kernel exploits aren’t that hard to find and it looks like this bug gives a path from kernel exploit to exploit persistence, with the only way to get rid of the persisted exploit is to throw away the CPU.
If I’m understand it right then, like, yikes!
It looks bad but this phrase looks even worse for AMD: "No fix planned"[1].
Finally internalizing themselves as the winner and starting to pull an Intel?
[1] - https://www.amd.com/en/resources/product-security/bulletin/a...
Edit after looking it up (leaving this comment in case someone else has the same question): Apparently microcode is in fact stored in the CPU itself and it does have permanent storage. The BIOS is only used for updating this internal memory and doesn’t transfer the microcode on every boot. I still wonder if the microcode patches are somehow validated/signed though, otherwise everyone with a kernel exploit could issue update commands to the BIOS with malicious microcode content?
How is a compromised AMD CPU better than Intel's CPUs which get damaged due to oxidation and high voltage?
There's no valid reason to not have this law. Any "intellectual property" excuses aren't going to fly, everyone already knows they're bullshit.
edited: slightly clarified legal possession
Related
Vulnerability in Popular PC and Server Firmware
Eclypsium found a critical vulnerability (CVE-2024-0762) in Intel Core processors' Phoenix SecureCore UEFI firmware, potentially enabling privilege escalation and persistent attacks. Lenovo issued BIOS updates, emphasizing the significance of supply chain security.
Secure Boot is completely broken on 200 models from 5 big device makers
Researchers from Binarly found that Secure Boot is compromised on over 200 device models due to a leaked cryptographic key, posing significant security risks until manufacturers issue firmware updates.
Compromising the Secure Boot Process
Researchers from Binarly revealed a security vulnerability in the Secure Boot process affecting over 200 device models due to a leaked cryptographic key, raising concerns about potential cyberattacks and security practices.
Secure Boot useless on PCs from major vendors after key leak
A study by Binarily found that hundreds of PCs from major manufacturers are vulnerable due to a leaked 12-year-old test platform key, allowing attackers to bypass Secure Boot protections.
New SLUBStick Attack Makes Linux Kernel Vulnerabilities More Dangerous
Researchers from Graz University of Technology developed SLUBStick, a technique that exploits Linux kernel heap vulnerabilities with over 99% success, enabling privilege escalation and container escapes against modern defenses.