Well, this whole topic has been beaten to death, so I will attempt to minimize my contribution.
Apple’s Security Update 2004-05-24 eliminates the need for my Help Viewer hack (see below). However it doesn’t close all of the URI scheme holes.
For details on that topic I’ll send you over to John Gruber at Daring Fireball.
Right! Now back to our regular scheduled programming..
The Mac net is a buzz with this news: There is a vulnerability in OS X that is potentially dangerous. When given a correctly structured (and possibly malicious) URL, Safari (and other browsers) can respond by asking the Help Viewer application to execute an AppleScript on a volume that is not the startup disk. When coupled with a disk image’s ability to auto mount after download we have a serious opportunity for a security exploit.
This is very reminiscent of the AutoStart worm from 1998 that took advantage of a security hole in QuickTime 2.0 and used to infect Syquest and Zip cartridges.
The first fix I documented just removed the execute privilege from the Help Viewer executable. This fix is a little more elegant and only disables AppleScript in Help Viewer.
cd /System/Library/CoreServices/Help Viewer.app/Contents
sudo cp Info.plist Info.plist.bck
sudo pico -w Info.plist
- Scroll to the bottom of the document and change the
There is a benign example of the exploit that you can use to test your systems.
via: macfantic in MacCentral’s comments
I bought my first "computer" in 1979; an RCA Cosmac VIP. It had a CDP1802 processor running at a staggering 1.7MHz and came with a whopping 1 KBytes of RAM, a video port (that required an hour of hand coding to initialize), and a hex keypad.
That’s just Great.
Now I’m compelled to go back and relive the trauma of programming in 1802 machine language. The event that made me avoid coding for 15 years… yeah, great