To view parent comment, click here.
To read all comments associated with this story, please click here.
It's not the slightest bit related to OS'es.
It's a weakness in the x86, which manifests itself with certain applications, like the X Server.
Running the X Server in CygWin on Windows is likely to be suffering from this particular vulnerability, as well.
The software bug is merely due to flaws in the hardware design, and in no circumstances related to the OS of choice.
It does not look like you actually read the article.
You need to read the article again.
If OS doesn't allow PIO access to user mode code, this exploit is not possible.
However, the article doesn't clearly say if you can carry out this exploit without root privilege or not. If this requires root privilege, then to me it is not a bug. Once you are root, you can exploit the system in whatever way you want. You can easily install a driver to get to kernel mode and do whatever the hell you want.
If on the other hand, a non-root process can do this, then it is definitely a serious bug in *nixes.
dylansmrjones: This exploit is not possible on Windows if you run X as a non-admin. Because a non-admin user mode process can never get PIO access and it can never install a driver to get in kernel mode to get PIO access.
BTW this is *NOT* completely a hardware bug. It is the OS which is giving permissions to sensitive areas first.




Member since:
2005-12-03
All operating systems running on x86 suffer from hardware vulnerabilities on the x86-platform. It takes a moron to believe otherwise.
No, it takes a moron to think this is x86 bug, when in fact it is an OS-level design flaw.
Windows does not suffer from this particular X Server bug because Windows does not use the X Server.
Windows does not suffer from this particular design flaw because it denies any user-mode (ring3) PIO access via EFLAGS.IOPL field. X Server is just an example - it could be any other app.
However, one cannot conclude on that background that Windows isn't vulnerable to hardware bugs.
I never claimed it wasn't. This is not a hardware bug.
Edited 2006-05-11 18:27