Apple patches vulnerability in Safari

Apple Computer Inc. issued an update on Friday to fix a reported security hole in its Safari Web Browser. The venerability, which was classified as "Extremely Critical" by security firm Secunia, allowed the execution of malicious code on the users computer.

"Apple takes security very seriously and works quickly to address potential threats as we learn of them — in this case, before there was any actual risk to our customers," said Philip Schiller, Apple's senior vice president of Worldwide Product Marketing, in a statement. "While no operating system can be completely immune from all security issues, Mac OS X's UNIX-based architecture has so far turned out to be much better than most."

The vulnerability, which has been confirmed using Safari 1.2.1 (v125.1) and Internet Explorer 5.2, made it "possible to place arbitrary files in a known location, including script files, on a user's system if the Safari browser has been configured to ("Open "safe" files after download") (default behavior) by asking a user to download a ".dmg" (disk image) file," according to Secunia's advisory.

While acknowledging the vulnerability, industry security analysts felt that people would not be at high-risk because exploit writers typically focus on writing such code for the higher-profile Windows-based computers.

"It seems to be that people just don't write exploits for the Mac because they're not as popular and they [the exploit writers] don't get much bang for the buck," Bruce Schneier, CTO of Counterpane Internet Security Inc., told MacCentral. "Historically these aren't that big of a deal, but that could change."

Security Update 2004-05-24 version 1.0 is available via the Software Update control panel.

Source: MacCentral



I stick my tong out at all those people that says Apple does not act fast for security updates. Those who run OS X, and actually use the Software Update feature, know that Apple release security updates when they are needed. I prefer the "when needed" philosophy over the "once a month" approach that Windows has been using lately (with the exception of the holiday season, of course).

Originally posted at Breaking Windows.

Article tags

Spread the word
Bookmark and Share
Profile image for ken-edwards

Article Author: Ken Edwards

Ken Edwards is the Gaming Editor at Blogcritics, and calls Breaking Windows home. Ken works part time for Student Publications at BGSU as the Webmaster and System Administrator. He is also a freelance web developer.

Visit Ken Edwards's author pageKen Edwards's Blog

Read comments on this article, and add some feedback of your own

Article comments

  • 1 - Michael Croft

    May 21, 2004 at 9:02 pm

    Some of the variant exploits still work. I recommend Unsanity's freeware Paranoid Android haxie. which catches them.

  • 2 - Ken Edwards

    May 21, 2004 at 9:17 pm

    yes indeed. the telnet exploit still exists. John Gruber suggested using RCDefaultApp.

  • 3 - Jim Carruthers

    May 21, 2004 at 9:29 pm

    I just ran Software Update and it offered to update my iPod stuff, which I don't own. I've already patched this exploit myself, but Apple has done dick.

    I've not seen any update to correct this exploit.

  • 4 - Jim Carruthers

    May 21, 2004 at 9:34 pm

    While I think about it, the problem ain't in Safari, it's in the WebKit, which affects all apps which use it, so all browsers, RSS readers, etc.

    The fix in the meantime is to disable the script functions of help: disk: and and so on.

  • 5 - Michael Croft

    May 22, 2004 at 12:41 am

    go with paranoid android, all. They have a whitepaper that explains why their approach is best. It catches any arbitrary protocol that is acting dodgy.

    Jim, i don't know why you don't see Security Update 5-24-2004. I do, and it fixes the well-known version of this issue. You might want to check again.

  • 6 - Mac Diva

    May 22, 2004 at 1:07 am

    Typo tease: You don't really' mean 'venerability' in paragraph one, Michael.

    I'll use the patch, just like I used last week's. But, the problems I've been having go beyond this. Safari has been continually crashing. In addition, graphics I post to my blogs while using Safari look misplaced in Internet Explorer. Then there is the garble at the bottom of the page about 20 percent of the time when looking at sites using Safari. In fact, if a page is prepared using Classic, it barely appears in Safari at all. As much as I like the speed of Safari, I still find it far from perfect.

  • 7 - Ken Edwards

    May 22, 2004 at 1:18 am

    Mac Diva - I have never heard of those Safari problems!

  • 8 - Mac Diva

    May 22, 2004 at 1:51 am

    I can show you one of them, now. Vist one of my blog friend's site using Safari. Let me know what you see.

    She would appreciate being able to fix this, though she will upgrade to OS X as soon as she can.

    I will post a photo example when I next look at my blogs in IE.

    For the record, I'm using Safari in Jaguar.

  • 9 - Ken Edwards

    May 22, 2004 at 1:59 am

    that looks like a lot of blue. a lot of LOUD blue.

    much different in IE.

  • 10 - Mac Diva

    May 22, 2004 at 2:39 am

    There should be content where the big blue expanse is, Ken. Writing, photos, etc. But, there isn't.

    Another example. Scroll to the bottom of the news story on this page and tell me what you see.

    Note: I don't mean only Ken. Anyone should feel free to help us figure this out.

  • 11 - Michael Croft

    May 22, 2004 at 10:20 am

    MD:--"typo tease: You don't really' mean 'venerability' in paragraph one, Michael."

    Erm, I didn't mean anything. Ken wrote this.

    RE: your friend's blog.

    Remove the unmatched <ul> tag from line 52 (in the generated code) of the sidebar and then Safari doesn't die.

  • 12 - Michael Croft

    May 22, 2004 at 10:57 am

    Also, I looked at the other site, and it's poorly written browser-detection code. If you have the debug menu on, tell that page your user agent is Windows MSIE 6.0 and it all works.

    Well written brower detection code tests for features and hides non-working pieces from them.

    Poorly written browser detection code tests for browser-names and makes assumptions on the basis of them.
    http://www.oregonlive.com/dhtml/hnavbar_class/scripts/hGlobal.js tests for navigator.appName, which is the bad way. It will also break for things like Konqueror, which (IIRC) doesn't return navigator.appName, since it is not (again, IIRC) in the DOM in the standards documents.

    This is the menubar control code for the top.

  • 13 - Jim Carruthers

    May 22, 2004 at 12:43 pm

    For some reason, the Security Update isn't showing up in my Software Update (I probably did something stupid like click disregard, or my iBook has been taken over by my evil twin). However, I downloaded the standalone patch from Apple. I'd already disabled help://

    Which while I think of it, is there an advantage to disabling or deleting the Help Viewer since I've never found it useful and it is slow as hell.

  • 14 - Ken Edwards

    May 22, 2004 at 3:01 pm

    "venerability" was penned by the folks at MacCentral, not me.

    There should be content where the big blue expanse is, Ken. Writing, photos, etc. But, there isn't


    Yea, I figured that out :P

    Changing my Safari User Agent things do work, thanks Michael.

Add your comment, speak your mind

Personal attacks are NOT allowed.
Please read our comment policy.
Please preview your comment.

blogcritics lists for Feb 14, 2012

fresh articles Most recent articles site-wide

fresh comments Most recent comments site-wide

most comments Most comments in 24hrs

top writers Most prolific Blogcritics for January

top commenters Most prolific Commenters in 24 hrs