To view parent comment, click here.
To read all comments associated with this story, please click here.
Not true. There are several attacks one could perform on a logged on system to gain full privilege later on by fooling the user into giving up his password. Depending on path settings, or specifics of the environment, you can create a script/program that masquerades as a legitimate higher privileged application and takes control next time the user performs that activity.
Maybe there are some mitigations already in the Linux environment that I don't know about. Do the DEs in some way protect shortcuts to important apps from tampering (e.g. the launcher icon for the package manager)? Is the path in the shell always ordered so that privileged directories come before unprivileged ones? Is there no way for a malicious program to reorder the path once it is established, or launch a sub-shell later on with a reordered path?
That's irrelevant. All it takes is one. Over many years of using different operating systems, the only machine I've ever had taken over remotely without any action on my part whatsoever was a Red Hat 9 box. The attacker had tampered with the PAM configuration, replaced /bin/login, and had about a dozen new accounts running IRC bots. I found evidence of one of those little script kiddie rootkit packages that you can download just about anywhere. This is not an attempt to damn Linux. The whole event was completely my fault for not keeping the system "up2date". The point is that hostile code exists for all platforms.
Remote code execution and privilege escalation exploits are becoming increasingly rare across the board these days anyway.
I assume it has something to do with the behemoth size of the company.
Given physical access to any machine without encrypted volumes, it is trivial for anyone with a moderate level of skill to install whatever they want on it.




Member since:
2007-02-17
The point is that the many many thousands of malware payloads that could use such an exploit are virtually all Windows executables.
Thank goodness. Why did it take Microsoft years to do that?
Nope. On secure systems, such a hostile person would require knowledge of a password in order to be able to elevate priveledges. On Windows 7, all that the same hostile person would have to do is click on 'allow'.