More Mac OS X Flaws Identified

Discussion in ' News Discussion' started by MacBytes, Apr 22, 2006.

  1. macrumors bot

    Jul 5, 2003


    Category: News and Press Releases
    Link: More Mac OS X Flaws Identified
    Description:: Apple is doing a lot of security patching of late, and it looks like its employees may be working overtime just to address some of the flaws founds by one security researcher.

    Posted on
    Approved by Mudbug
  2. macrumors 603


    Jan 28, 2005
    American Riviera
    I'm no professional, but these look like pretty serious flaws, from what I understood from the article. By 'crashing' Safari, could a further exploitation be performed, or is it only an annoyance? It looks like I need to get educated about this stuff now.


    500th post
  3. macrumors 6502a


    Jan 4, 2002
    Austin, TX
    Just more scare tactics from some "security" researcher in the wild who wants his 15 minutes of fame.

    Crashing by itself is not a security threat. The security "experts" tack on "and may allow an attacker to execute arbitrary code" to serve up the FUD to the public and to coerce the OEM to fix the bug.

    Just about any app will crash on malformed data files unless it has numerous integrity checks at all levels, which add complexity and additional time to do some otherwise rudimentary task.

    In the end a lot of hackers use social engineering to coerce a target to allow access, such as the ever-popular phishing scams that have been around as long as average users have needed a password to log on to something.

    More likely than not a malformed graphic will crash your browser. Big deal. On the PowerPC its very, very hard to get random code to execute and on the Intel CPU in Macs the OS sets the CPU to not execute random bits of code floating around on the heap/stack.
  4. macrumors regular

    Sep 20, 2003
    The article is kind of confusing. It said there were 6 zero-day exploits found this week but goes on to say at the end that Apple was notified of the them in January and February. How can you find something now and say you reported it on awhile ago?

    Also, doesn't the term "zero-day exploits" mean an exploit undiscovered either by the company or security professionals? They fact that they're reporting it doesn't make it a zero-day exploits coupled with the fact that Apple became aware of it in January. That's what makes "zero-day"'s so dangerous. No one in the public knows about it and it's being used.
  5. hob
    macrumors 68020


    Oct 4, 2003
    London, UK
    This article seems to gloss over the details - I'm not sure whether to be concerned or not!

    For the time being, I'm not! (judging by my 3 years experience of macs - 0 viruses so far!)
  6. Moderator emeritus


    Jan 9, 2004
    Grand Rapids, MI, USA
    I'm confused about these things to. I think here, what is meant is that this individual claims to have not only a vulnerability but an exploit mechanism that takes advantage of that vulnerability (as opposed to a vulnerability that may contribute to something bad being done, but isn't enough, without additional information, for anyone to create an exploit... like when something "might" cause arbitrary code to be run under some conditions that "could" occur...). And apparently this individual's "proof of concept code" is the proof of that.

    As far as the Jan/Feb thing, I think the article means that the bugs were disclosed in January or February, and were apparently zero day at the time, but are being made *public* now.

    But I think all the zero day means here is that there is a usable exploit based on these vulnerabilities. Which...well... I think it's good that it's in Apple's hands, and also in the security communities hands. :)
  7. Moderator emeritus


    Jul 28, 2003
    Citizens Bank Park
    I'm not sure how to take this either (because I'm not sure it's a exploit or not), but I am definitely not concerned with it. Never be worried about newly found bugs, security holes, etc. Contrary to popular belief, finding bugs is a good thing. Anyone in software development knows that bugs are expected in software. It doesn't matter how good of a programming team you have, bugs will be introduced into the project. Finding bugs means that Apple can fix them before someone can figure out how to exploit them. If a hacker finds them first, then you have to worry.
  8. macrumors 601


    May 29, 2005
    I highly doubt we have anything to worry about.
  9. macrumors 68040


    Mar 4, 2006
    Kent, UK - the 'Garden of England'.
    I am pleased that there continues to be interest in the security of Mac OS X. Security by obscurity is no way to go, so it's best that any gaping faults are fixed now - especially what with the Intel transition opening up the possibilities of gains in market share, so making Mac OS X users more of a target in future malware releases.
  10. macrumors G5


    May 2, 2002
    I'm all in favor of researchers looking for bugs and reporting them to Apple. No OS will ever be 100% perfect, but Mac OS X can only be the best it can be if people are looking for things that need to be fixed.

    And of course, such issues should be reported to the public AFTER they have been patched (or after the OS vendor has refused to fix them perhaps).

    Some perspective:

    Windows XP Home:
    23 out of 116 advisories, rated up to Highly Critical, are marked as unpatched by Secunia.

    XP Professional:
    27 out of 131 advisories, rated up to Highly Critical, are marked as unpatched.

    Internet Explorer 6.x:
    19 out of 99 advisories, rated up to Moderately Critical, are marked as unpatched.

    Safari 2.x:
    1 out of 3 advisories, rated up to Not Critical, are marked as unpatched.

    Mac OS X:
    1 out of 69 advisories, rated up to Highly Critical, are marked as unpatched.

    Let's get that zero back ASAP! :)
  11. Moderator emeritus

    Jun 25, 2002
    Gone but not forgotten.
    You should always have some worry, even if it says there aren't any security flaws unpatched. A couple of days ago, the problems were there but no one knew about them. Would an attack be any less problematic?
  12. macrumors member

    Aug 27, 2005
    It's ironic that Safari crashed on me the first time I opened the link. Grrrrrrrrrr
  13. macrumors 6502a

    Jan 8, 2005
    Why do people make silly comments like this, if it was so "Highly Critical" then I'm sure Apple would fix it. Personally it doesn't bother me in the slightest. Not compared to the infinite viruses and such when I used windows.
  14. Moderator emeritus

    Jun 25, 2002
    Gone but not forgotten.
    A lot of people have undying, and sometimes, unwarranted faith in Apple. Apple are automatically the good guys because they're not the bad guys, right?

    The problems with Preview opening a .bmp file and it having Mac OS X executable code in it is highly unlikely but should someone decide to do it, it could be devastating. I'm sure that there are plenty of them with Windows executable code in them already. The fact that there is also a problem with TIFFs makes it more of an issue for Mac OS X users.

    We don't have to worry as much, but we still have to worry.
  15. macrumors 68020


    Dec 4, 2005
    Still here.
  16. macrumors 68040


    Mar 24, 2003
    Couldn't agree more.

    Did you guys read the rest of of the reports by them? It shows the other "flaws" they reported, and how Apple patched them within a very short time.
  17. Moderator emeritus

    Jun 25, 2002
    Gone but not forgotten.
    It's the time between when the flaws were available and the time they're exploited that bothers me, not the time between when they were reported and patched.

    We're lucky so far. Now that people can run WinXP and Mac OS X on the same machine, they might decide that it's easier to create exploits simply because it is.
  18. macrumors regular

    Feb 21, 2006
    Norwich UK

Share This Page