According to US-CERT, AMD's graphics drivers are responsible for a serious hole in Microsoft's Windows security systems.
AMD has been accused of making Windows unsafe, thanks to graphics drivers that fail to operate when Address Space Layout Randomisation (ASLR) is enabled.
Introduced by Microsoft to guard against code execution through buffer overflow attacks, ASLR works by shuffling the memory map and storing critical resources in a pseudorandom location. The result: if an attacker attempts to overwrite a specific section of memory with a buffer overflow or similar attack, that memory location will be different on each targeted system.
Combined with Data Execution Prevention (DEP), which marks sections of memory containing program data as non-executable to minimise the risk of a buffer overflow writing to an area of memory which can then be executed as a program, ASLR is an effective defence against many forms of attack.
Unlike DEP, however, ASLR is disabled by default and only activated by manually toggling a registry key marked 'unsafe' or using Microsoft's optional Exploit Mitigation Experience Toolkit (EMET) add-on. Doing so on systems with AMD graphics cards, however, has an unwanted side-effect: system crashes.
According to a vulnerability notice published by the
US Computer Emergency Readiness Team (US-CERT) late yesterday, AMD's graphics drivers are incompatible with ASLR and cause blue-screens when the functionality is enabled. Drivers for graphics boards from rival Nvidia, and those designed for Intel's integrated graphics systems, work fine with ASLR.
According to US-CERT's analysis, the result is that systems are ill-secured against attack. Worse, a feature which should be activated by default in order to provide the most security is disabled and hidden - leaving Microsoft with the blame for security breaches it has already coded protection against.
US-CERT's advice is clear: for server systems with AMD graphics hardware, where video performance is a non-issue, users should consider moving to generic VGA drivers which fully support ASLR. For other users, who specifically bought the AMD graphics board for 3D tasks and intend to use it to its full advantage, US-CERT has only one suggestion: '
If the video adapter on your system is not compatible with EMET "Always on" ASLR, consider using a different video adapter that has ASLR compatible drivers.'
20 Comments
Discuss in the forums ReplyIt is a problem with a feature that is disabled by default. This is not to say that AMD's drivers aren't crappy - they are, but blaming them for incompatibility with somthing that is disabled by default and apparently isn't used anywhere is like complaining about 3D acceleration not working in DOS version of Tomb Raider compiled for Glide ...
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EMET\EnableUnsafeSettings
and if you dont have the optional and downloaded from MS EMET you dont have the reg key anyway (not present on my GTX 480 system)
In order for a buffer overflow attack to happen, you must already be executing some malicious code, which should have been caught by other security measures. Of course it IS reasonable for those security measures to fail, but ASLR still isn't a critical first-level security feature, and it could have observable performance costs, so it isn't enabled by default.
All AMD is 'guilty' of, is not testing their drivers with an obscure security feature that drastically changes the way system-level addressing works on a tiny fraction of systems, which MS themselves have chosen NOT to require driver makers account for. US-CERT is just being dramatic and accusatory.
Shouldn't be an issue. Both AMD and Nvidia release regular driver patches.
If you are careful you shouldn't get a virus anyway. Can't remember the last time I got one. Only ever clean them off other peoples computers.
:D :D
Nah - Microsoft does that job very well already. And if they have a bad day, Adobe comes to the rescue.
That is why everything from planes to fission-powered submarines and hydroelectric dams should run on ATI hardware! Conspiracy! Get the tinfoil hats!
i don't see why they are blaming amd
windows is a piece of **** from a security standpoint
dep is useless, so disabled it same as uac. havent had any problems/viruses in over 6 months thanks to my third party security
One could argue that AMD has a problem if ASLR support is indicated, yet hasn't been tested to work properly, but I wouldn't call it poking a hole in Windows security.
It is particularly important for low level drivers with privileged access such as graphics drivers. Intel and Nvidia support this, AMD don't. I presume they were asked nicely (standard has been out for a while) but they ignored the requests so they are now being publicly bashed in an attempt to get them to comply.
None of this matters to us of course as we don't have this setting turned on, but it matters in a big way to AMD if they want to sell any PC's with their chips in to the US government who have higher security standards.