Access member only content, take part in discussions with comments on blogs, news and reviews and receive all the latest security industry news directly to your inbox. Join now for free.
A confirmation email has been sent to your email address - SUPPLIED EMAIL HERE. Please click on the link in the email to verify your email address. You need to verify your email before you can start posting.
If you do not receive your confirmation email within the next few minutes, it may be because the email has been captured by a junk mail filter. Please ensure you add the domain @scmagazine.com.au to your white-listed senders.
Randy Abrams, director of technical education at ESET, described AutoRun as the ‘longest standing unpatched Microsoft vulnerability' that Microsoft calls a ‘feature'.
Abrams explained that AutoRun allows a computer to be run by a person with no knowledge of IT so when you use removable media, Windows will automatically look for a file called ‘autorun.inf' and if it is there then Windows will do what the file says to do.
This would mean that if a user doesn't have the know how to double click on setup.exe, they just put a CD or USB key in and the program will run itself.
Abrams said: "The problem is that the bad guys know that and often use AutoRun to install malicious software as soon as a USB drive is plugged in. Conficker exploits this as well.
"In 2008 more than one out of every 15 threats we detected were using autorun.inf to help infect users. In January, nearly one out of every 10 threats we detected at ESET used AutoRun.
"Microsoft does not provide a truly effective solution for disabling AutoRun and the partial solution they suggest is cumbersome."
Abrams explained that fixing this requires creating a registry key, which involves saving the file as a plain text file, not a document that must be .reg. Alternately you can create the registry key by hand.
Abrams said: "The Microsoft solution is ineffective and breaks Windows Media Player. When you use Microsoft's solution, each time you change a CD for Media player you have to close and re-open Windows Media player for it to recognise the new disk. With the solution I am suggesting Windows Media Player still recognises when you change a disk."
To begin commenting right away, you can log in below or register an account if you don't yet have one. Please read our guidelines on commenting. Offending posts will be removed and your access may be suspended. Abusive or obscene language will not be tolerated. The comments below do not necessarily reflect the views or opinions of SC Magazine, Haymarket Media or its employees.