Slashdot Mirror

← Back to Stories (view on slashdot.org)

Apple Responds to MOAB

Posted by CmdrTaco on from the that-was-pretty-fast dept.

frdmfghtr writes "Apple has released what appears to be the first security update as a result of the "Month of Apple Bugs." While the Apple site doesn't explicitly say that the fix was a result of the MOAB, it does point to a sample Quicktime file that triggers the overflow flaw (well, sort of...it says the file is there but doesn't provide any links)."

2 of 126 comments (clear)

  1. Re:MOAB? by djh101010 · · Score: 0, Redundant

    "Hey everybody! Check out our new weapon! It's the MOTHER of ALL BOMBS!!!"

    MOAB == WMD.

    Y Um, no. WMD has been defined, for quite some time, as chemical, nuclear, and biological weapons. But by all means, do carry on.
  2. Re:So...Is The QT Flaw the Only Notable Bug? by Warlock7 · · Score: 0, Redundant

    You might want to discount the QuickDraw bug to. I don't think that OS X uses QuickDraw at all, I believe that's fundamentally an OS 9 item, which is no longer a supported OS.

    Note: The QuickDraw API is deprecated in Mac OS X v10.4. That means that Apple no longer plans to develop QuickDraw software or documentation. There is no better time than now to completely remove QuickDraw code from your application.

    So, you might want to shorten the list again. You'd have to remove MOAB-23-01-2007 - the "Apple QuickDraw GetSrcBits32ARGB() Memory Corruption Vulnerability".

    I suppose that you could leave it on the list, as this is an Apple bug, but to include a deprecated API call makes me wonder.