Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Apple Fixes Safari "Carpet Bomb" Windows Vulnerability

Posted by kdawson on Fri Jun 20, 2008 08:15 AM
from the no-more-carpet-tax dept.
Titoxd writes "Apple has released a new version of Safari that fixes the carpet bomb vulnerability in Safari 3.1 for Windows. This comes in the heels of Microsoft recommending against using Safari in Windows, as well as the release of code exploiting this vulnerability."
+ -
story

Related Stories

[+] Apple: Microsoft Urges Windows Users To Shun Safari 502 comments
benjymouse writes "The Register has picked up on a recent Microsoft security bulletin which urges Windows users to 'restrict use of Safari as a web browser until an appropriate update is available from Microsoft and/or Apple.' This controversy comes after Apple has officially refused to promise to do anything about the carpet bombing vulnerability in the Safari browser. Essentially, Apple does not see unsolicited downloads of hundreds or even thousands of executable files to users' desktops as being a security problem." Now while downloading a hundred files to your desktop won't automatically execute them, Microsoft's position is that a secondary attack could execute them for you.
[+] Apple: Safari "Carpet Bomb" Attack Code Released 118 comments
snydeq writes "A hacker has posted attack code that exploits critical flaws in the Safari and Internet Explorer Web browsers. The source code can be used to run unauthorized software on a victim's machine, and could be used by criminals in Web-based computer attacks, security experts say. The public example of the attack code allows attackers to litter a victim's desktop with executable files, an attack known as 'carpet bombing.' In combination with bugs in Windows and Internet Explorer, attackers can run unauthorized software on a victim's computer."
[+] Safari "Carpet Bomb" Attack Still a Risk 117 comments
SecureThroughObscure writes "Just a short time after Apple's recent acknowledgment of and patch for the Safari Carpet Bomb 'blended' IE flaw, Microsoft researcher Billy Rios shows that Safari is still useful in a blended attack, this time with Firefox 2/3. (ZDNet's Nate McFeters also spread the word.) Rios claimed that he is able to use Carpet Bomb, despite the recent patch, to steal arbitrary files from victims who also have Firefox 2/3 installed. Both Rios and McFeters pointed out that Apple, which took some heat for not originally patching, actually did a good job of addressing the issue, as the code execution angle was not originally understood (the details came out later). Rios is withholding details of the new attack vector until Apple has had time to patch or respond to this issue."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • You mean? (Score:5, Funny)

    by Centurix (249778) <mrjolly@op t u s n e t . com.au> on Friday June 20 2008, @08:19AM (#23871981) Homepage

    You think the carpet bombers did this?
    Face it man, that rug really tied the room together...

  • by Anonymous Coward on Friday June 20 2008, @08:23AM (#23872025)

    And my computer rebooted into OS X. Not that I mind, really.

  • Did they fix the bug where Safari installs as an iTunes update? I'd say that that is a fairly severe bug right there.
    • by tokul (682258) on Friday June 20 2008, @08:53AM (#23872479)

      Did they fix the bug where Safari installs as an iTunes update?
      New (released more than one month ago) Apple Software Update has two sections. One for updates and other for new software. When Safari was introduced, Software Update had only one section.
      • by Briareos (21163) * on Friday June 20 2008, @09:27AM (#23872929) Homepage

        New (released more than one month ago) Apple Software Update has two sections. One for updates and other for new software.
        Last I checked the "new" software was still checked by default - and I really don't feel like installing anything that ASU comes with right now. So does anyone know if they finally fix THAT idiocy?

        np: Seabear - Sailors Blue (The Ghost That Carried Us Away)

        • by 99BottlesOfBeerInMyF (813746) on Friday June 20 2008, @09:58AM (#23873365)

          Last I checked the "new" software was still checked by default - and I really don't feel like installing anything that ASU comes with right now. So does anyone know if they finally fix THAT idiocy?

          Why would they need to "fix" it. It is operating as they prefer it, the same as all the software MS includes in Windows that most of us would prefer we did not have to install. Is it so difficult for you to uncheck that box if you're performing an update?

          • by torchdragon (816357) on Friday June 20 2008, @10:29AM (#23873813) Homepage

            Yes.

            Recently, the Java update software has begun asking for the Open Office installer to be installed on the system during an update for Java. Several users at my company have clicked straight through and added more crap to their desktop/registry/uninstall information.

            Can we blame the users for not reading every detail and not unchecking a checkbox? Yes.
            Can we also blame software vendors who are relying on the aforementioned user behavior to add their software to your computer on the sly? Yes.

            Its a bad practice and it needs to stop.

            If something is required for the operation of a software package, default to selected.
            If something is optional or not required for the operation of a software package, default to unselected.

            Why are we allowing marketing to override good engineering?

            • "Is it so difficult for you to uncheck that box if you're performing an update?"
              "Yes."
              Then you are exactly the kind of "lowest common denominator" type to whom the default yes was targeted.
              • Actually, I'm not. They don't want to hit me with that checkbox because I do pay attention to what comes up on my screen. So instead of getting an extra incidental hit for whatever they're pushing, they now have an annoyed customer. The people they're targeting with this is the people who won't notice that they're installing extra software.

                So far Apple, Sun, and Daemon-Tools have all edged me away from their products because of this choice. Though I suppose you really can't be concerned with the dolphins ge

          • by lusiphur69 (455824) on Friday June 20 2008, @10:38AM (#23873961) Homepage

            The real question is why are you defending Apple's unethical bundling - when the same is performed by Microsoft we criticize it. Call a spade a spade or you look foolish. Face it, this kind of practice is unacceptable, whether or not it comes from your favorite company.

            Is it so difficult for you to uncheck that box if you're performing an update?
            For me, no. For millions of uneducated end users, it is. Get it?
            • Re: (Score:2, Insightful)

              I guess it's about as unethical as Microsoft forcing IE7 on all users who use automatic updates. If fact, Microsoft forces new stuff all the time this way.

              Not defending it - just saying that Apple, Microsft and Sun all do this, so don't single out Apple as being unethical in this manner.

              • by Anonymous Coward on Friday June 20 2008, @12:36PM (#23875735)
                No, it isn't like that. IE7 is an upgrade to something already installed and, to most end-users, in use. Safari is an entirely new piece of software. There's a difference, whether you like it or not.
                • Re: (Score:3, Insightful)

                  Nevertheless, IE7 broke a bunch of stuff at my company. The IT folks spent a considerable amount of time and and energy getting everything on the intranet working with it.

                  I would strongly argue that IE7 was a new product with a similar name, and not an upgrade.

    • I installed Safari for Windows about a week after it came out. That was several months ago.

      It was very clearly marked as "new software". It was not marked as an update to anything. I just checked on a different system, and Safari is still marked as "new software".

    • Did they fix the bug where Safari installs as an iTunes update? I'd say that that is a fairly severe bug right there.

      More importantly, did they fix the ipod software itself? Every update cripples me even further without fixing what the previous broke (80GB gen 5).

      1. IPOD plays all songs
      2. IPOD needs to be restarted after adding songs
      3. IPOD cannot have more than ~30,000 songs in a genre
      4. IPOD cannot have more than 30,000 songs in TOTAL (otherwise no songs display)

      I'm afraid of the next update, where I can only have 1 song total on it.

      Believe me, the support is sub-par to say the least. The online help is very confusing: sc [imageshack.us]

      • Well, Safari isn't exactly embedded, but it's handy if you want to download Firefox or Opera and then make one of those your default browser...

  • by sakdoctor (1087155) on Friday June 20 2008, @08:33AM (#23872167)

    It's pretty common that some badly configured web server will send content to me that firefox will then ask if I want to download.

    Just letting it download and then moving on to the next file is...well such an obviously stupid behaviour.

    Also, please don't let carpet bombing become the next security buzzword along with bricking and zero-day.

    • Just letting it download and then moving on to the next file is...well such an obviously stupid behaviour[sic].

      I disagree. If I click a link to download something, well obviously I want to download it. Clicking a second time to confirm is an annoyance. Apple's solution is to let things download, but put them in the downloads folder and flag them as untrusted content from the internet (well not flag them as trusted, since the default is untrusted). That is to say, that is their solution on OS X. On Windows, there is no download folder and for some reason they screwed up and did not flag it as untrusted in Vista (XP

      • Apple's solution is to let things download, but put them in the downloads folder and flag them as untrusted content from the internet (well not flag them as trusted, since the default is untrusted). That is to say, that is their solution on OS X. On Windows, there is no download folder and for some reason they screwed up and did not flag it as untrusted in Vista (XP does not support that either). In my mind, their solution on OS X is superior, because it also helps solve the problem of executables masquerading as data.

        Actually, Windows has this as well.

        If you download a file using Internet Explorer, an NTFS file attribute is set that marks it as "downloaded - untrusted". Double click the file and you get a popup asking "DO you want to run this executable?" with a popup and showing the executable properties (signed by, etc). Problem is, it requires that you run NTFS, and if you copy the file to a network server, that network server to support extended attributes. Use Firefox or other browser, and the attribute isn't set, or copy to a fileserver that doesn't support extended attributes, and it's lost.

        (Most frustrating when you have to apply 12+ patches to a program that Microsoft Update doesn't have support for. I wrote a little bash script that shells out cmd.exe (was an MSI file) to do this, but you're still left with these popups).

        As for OS X, I believe these notifications started in Leopard. They too are extended attributes, I believe. Though I think OS X copies attributes to filesystems/servers that don't support them by using dotfiles, so copying the file around doesn't get rid of it. (It goes away after you've approved it, though. No reason why Apple couldn't figure out what flag IE sets and have Safari do same on Windows, either.

      • If I click a link to download something, well obviously I want to download it. Clicking a second time to confirm is an annoyance.

        True, but that's not the only way to get it to download. As the proof of concept code [liudieyu.com] showed, all you have to do is put it inside a hidden iframe. If I go directly to a url ending in .dll, this might be excusable, but definitely not with an iframe.

      • Re: (Score:3, Informative)

        Actually, Vista -does- have a specific Download folder now, for the record.

  • Did Microsoft fix the vulnerability caused by Internet Explorer running with its current directory set to the Desktop and its library search path going through the Desktop? Because until they do that, the actual vulnerability in Windows that Safari made slightly easier to exploit still exists.

    • The actual vulnerability is that Safari downloaded files without the user's permission. Trying to make this a Windows issue smacks of fanboyism.

      • It isn't a mutually exclusive situation. There are two disparate vulnerabilities here. By themselves they aren't that big of a threat , but when used in concert the threat is greater than the sum of it's parts. You need the IE issue to load the compromised dll and you need Safari in order to "secretly" download the compromised dll in the first place.

        • By themselves they aren't that big of a threat

          Um, yes, the IE flaw *is* that big of a threat. There is no circumstance where it should EVER be acceptable for a downloaded file, whether with permissions or not (who other than a geek is going to worry about downloading a file called "somethingobscure.dll"?), to be AUTOMATICALLY executed just because of the name it's given.

          I hope Microsoft fixes it bloody quick.

      • by gad_zuki! (70830) on Friday June 20 2008, @12:24PM (#23875553)

        How did safari even get on most of those computers. I think people are seriously missing the big issue here.

        Imagine if Netscape won the browser wars and you installed Windows Media Player which later on, in the middle of then night, downloaded and installed IE for you. If Office 2008 did this on OSX there would be riots in the street. When Apple does it, its of course Microsoft's fault.

        Granted, there's a lot of blame to go around, but claiming this is a MS problem is being pretty unfair and only shows up that Apple can do anything, and few will complain.

        • Imagine if Netscape won the browser wars and you installed Windows Media Player which later on, in the middle of then night, downloaded and installed IE for you.

          Except that iTunes didn't "in the middle of the night, download and install Safari".

          However Microsoft did force IE into Windows, using techniques that created many inherent security flaws that we are still battling 11 years later, this being one of them.

          Apple can do anything, and few will complain.

          When Apple fucks up, I'll be the first to complain.

      • The actual vulnerability is that Safari downloaded files without the user's permission.

        Asking for permission before doing something that may potentially lead to a security exploit is no protection at all. Seriously. In the eight years between the time Microsoft introduced the browser-desktop merge, and the time I quit being a system admin and went back to programming, I had many many cases where some user (and these weren't dumb users, these were engineers and programmers with PhDs and patents to their name) would come to me and say "Peter, I just clicked the wrong button again, and I think I have a virus". That "again" is important. That means that they have the "Windows pops up stupid dialogs all the time so I have to approve this one" reflex burned into their cortex.

        A user is not going to realize that a web page asking to download "someobscuregibberish.dll" is attacking them.

        Stupid permission dialogs are no protection.

        The actual vulnerability is twofold:

        1. The path goes through the current directory by default, and it goes through the current directory first.

        This is something that UNIX used to do, and it was widely recognized as a BAD idea by 1980. MS-DOS wasn't even out yet, let alone Windows.

        2. The default download directory is the default directory of any program, let alone a program that is run virtually every time you log in.

        This one is, well, beyond stupid. This is like having the mailslot in your front door connect to your safe deposit box. The directory that is MOST likely to contain malicious code is the one that you're MOST likely to be running code from on any given day.

        Trying to make this a Windows issue smacks of fanboyism.

        Name one other operating system or application where downloading files to the default download folder would cause them to be run, under any normal circumstances. The whole idea is completely insane.

    • Sure, Microsoft will fix this, in about 2 years.

      I guess this proves how important they consider security these days. Does anybody still believe anything that they say? Yes, I really believe they have given up the fight over ODF.

  • Hmm? (Score:5, Insightful)

    by koinu (472851) on Friday June 20 2008, @08:38AM (#23872221) Homepage


    Safari downloads files (e.g. dynamic libraries) in user directories where the Internet Explorer could autoload them on start. Isn't the bigger problem within Internet Explorer? Why did Microsoft setup a library path to a user's directory at all?

    • Microsoft's library path ALWAYS goes through the current directory. For some obscure reason that IE icon on the Desktop, the one that isn't a shortcut but is actually something special Microsoft added back in 1997 to make it harder to remove IE, runs IE on the Desktop instead of in the IE install directory, the way it would if it was a shortcut.

      It's all a side effect of Microsoft's shenanigans when they tried to use browser-desktop integration to make an end-run around their agreement with the US DoJ. That they've convinced people that the big news is a bug in Safari that makes it slightly easier to take advantage of this problem is, well, bizarre.

      And now you know the rest of the story.

      • You can't get around this by avoiding the "special" IE icon, though. You can make a real shortcut, set the working directory to whatever you want, or even launch IE from its own program directory from a command prompt, and it will still consider the desktop to be the current directory.

        As a fun experiment,

        • copy cmd.exe to the desktop and rename it to notepad.exe
        • launch IE the "safest" way you can think up
        • view page source
        YRMV, but in my tests with IE 6 and 7 in 2k and XP, it will launch the command prompt instead of notepad, and you can see the current directory and the stuff it prepends to the PATH variable.

        Until this is fixed in IE, I recommend copying notepad.exe and all your system .DLLs from the system32 directory onto each user's desktop, and use an ACL on each one to make sure your users do not have permission to overwrite them. No, seriously. (Or you could just use another browser.)

        • Re: (Score:3, Funny)

          You can make a real shortcut, set the working directory to whatever you want, or even launch IE from its own program directory from a command prompt, and it will still consider the desktop to be the current directory.

          Whiskey Tango Foxtrot?

          Every time I think I'm being to hard on Microsoft, that I'm just being a cynical old fart, I come across something like this.

          Holy Mother of Turing, what were they thinking of?

      • Microsoft's library path ALWAYS goes through the current directory.

        This isn't true. If an application calls SetDllDirectory(), it overrides the search path. The order becomes:

        1. The directory the application loaded from.
        2. The directory specified as a parameter to SetDllDirectory()
        3. system directories (order elided)
        4. PATH directories (Worthy of an if-I-had-a-time-machine-shooting.)

        The above function is highly useful to force a single specified path (it takes ONE path, not a list) early into the DLL load search order. It's pretty much necessary to use this to avoid getting screwe

        • Apologies for the reply-to-self, but I forgot to mention another important special-case use of SetDllDirectory(): if passed the empty string, it removes the current directory from the DLL search path. So even if your app doesn't require some particular directory to be 'blessed', this call can still mitigate a variety of DLL-related risks.

        • Will that also override the application search path going through the current directory?

    • Re: (Score:3, Interesting)

      This issue has been avoided in UNIX systems for decades I believe. I remember when I was first learning about the command-line that I thought it was strange you couldn't just compile a new program and type $ a.out to launch it. That's because the current directory is not in the path. You have to type $ ./a.out to get the executable seen. The reason this is a system default is to prevent someone sneaking in a malicious copy of a system command such as ls into a directory where you'd accidentally use the fake

  • Damn... (Score:3, Funny)

    by PawNtheSandman (1238854) on Friday June 20 2008, @08:48AM (#23872403)
    All I know is if someone broke in my apartment and pissed all over my rug, I'd be pretty upset.
  • While I am no Microsoft fan, I am amazed at the hubris of comments in this thread.

    Surely anyone with half a brain HAS TO ADMIT that the Safari vulnerability is FAR WORSE than IE setting it's current path to the windows desktop.

    In fact, the Safari vulnerability can be exploited for root access to the box without IE being in the equation AT ALL. Just pick some program or two that are likely to be installed on any user's computer ( iTunes, Firefox? ), and download .exe files with those names to the desktop. *B

    • by 99BottlesOfBeerInMyF (813746) on Friday June 20 2008, @09:55AM (#23873327)

      Surely anyone with half a brain HAS TO ADMIT that the Safari vulnerability is FAR WORSE than IE setting it's current path to the windows desktop.

      Certainly not for the average Slashdot user and arguably not for anyone. Safari won't overwrite a user's existing icons, just add new ones. I also opens a download manager so users know something is being added. There are some pretty ignorant users out there, but not many that won't take not that some random Web site is downloading something called "Firefox.exe" to their desktop with an icon that looks just like their Web browser's. Finally, I notice you use the present tense. The ability to do this in Safari has been fixed, whereas the flaw with Windows has not. So, yeah I'd say the flaw in Windows is currently a FAR WORSE vulnerability, as you put it.

      The main thing here, is the Safari flaw requires user interaction to work by itself, which means you have to manage a social engineering feat and get people to do something (double click and icon). With the flaw in Windows, any download from any source that they can get on a user's desktop can be automatically run.

      • Re: (Score:2, Insightful)

        Safari won't overwrite a user's existing icons, just add new ones. I also opens a download manager so users know something is being added. There are some pretty ignorant users out there, but not many that won't take not that some random Web site is downloading something called "Firefox.exe" to their desktop with an icon that looks just like their Web browser's

        This is a laugh an a half. I am pretty sure if I took an informal survey of my acquaintances many would not even know what a download manager was if

        • For example, if you hit WIN+R and type 'CMD", the desktop is your default working directory.

          No, it's your user directory, one level up from your desktop. Much harder for crap to end up there by accident, though it does happen (fools are ingenious, etc.)

          Running from the WIN+R prompt searches the path like it should, and will not run things from the desktop unless it's been added to the path.

        • I am going to go out on a limb here and even argue on MS's side, in that IMO, this is not an IE flaw at all. No one should give a rat's ass what the working directory of any application is because it can be changed at will anyway - that is the whole point of a "working directory". If your security model relies on the fact that an application never has the working directory set to an alternate location, then you have big problems.

          I agree 100%. In fact, I'll go one step further and say that any application

        • People nowadays just instinctively close the download manager window, both in Firefox and Safari.
          Now I agree with your point that we need to imporve buy is that the same way that people click Save File in IE/Firefox or are we talking about different instincts?
    • There's plenty of face-egg to go around. Safari's drive-by download functionality is certainly idiotic, but it's just plain dangerous to have the user desktop be the place for 1) program shortcuts 2) random crap that tends to appear automatically and pile up with or without Safari's help (and, in the default config, with file extensions hidden) and 3) the built-in unremovable web browser to try to load libraries from, even though there's not the slightest reason that library files should ever be there.
    • Which brings up two other points. Whose idea was it to download to the desktop anyway?? Maybe to a downloads folder on the desktop . . but man what a bad idea.


      Almost as bad as having the desktop be a swamp of shortcuts to programs. Start menu anyone? Windows desktops of the average user remind me heavily of MySpace.