MoAB #3: Apple Quicktime HREFTrack Cross-Zone Scripting vulnerability

“The third instalment of the Month of Apple Bugs is less impressive than the first two, since it is apparently just a new way of exploiting a known vulnerability in QuickTime (as previously used by the MySpace XSS QuickTime worm),” Stephen Withers reports for iTWire.

Withers reports, “The disclosure page does not indicate whether the Mac OS X version of QuickTime is affected as well as the one for Windows, and the proof of concept appears to rely on other Windows vulnerabilities. Furthermore, the exploit is described as a ‘cross-zone scripting attack,’ which is a Windows concept.”

Full article here.

LMH’s MoAB #3 page here.

MacDailyNews Take: Month of Apple Bugs: In like a paraplegic kitten, out like a…

Related articles:
MoAB #2: VLC Media Player udp:// Format String Vulnerability – January 03, 2007
MoAB #1: Apple Quicktime RTSP URL Handling Buffer Overflow Vulnerability – January 02, 2007

25 Comments

  1. So far all of the supposed vulnerabilities have been so minute that I would hardly call them anything but future minor fixes. The second one didn’t even have anything to do with Apple as it was a bug in VLC player not Apple’s software.

    The whole thing is to get hits on this persons website I’m sure. Because so far nothing even comes close as to something that anyone should even think of as a vulnerability.

    It’s a fricken sherade if you ask me. I’m not in impressed at all. And I know OSX is safe.

  2. Well, I guess it IS a month of “Apple” bugs, so since QuickTime is made by Apple and is some of the oldest and most convoluted code still being maintained by Apple (most still in Carbon), it would make sense that some of these have slipped through the cracks.

    From the FAQ
    “And the reward (automated responses and euphemism-heavy advisories) doesn’t pay off in the end.”

    This is the point of the entire excercise. Apple doesn’t bend over backwards for their finding an exploit with an improbable vector (while they’re actually working on fixing more likely scenarios reported by responsible researchers) and they’re tired of getting sand kicked in their faces by the researchers who get their names tied to advisories given by Apple. Left with nothing to be proud of, they go to the public to say that “AAAHHH! DANGER!!! Retail water bottles when refilled contain bacteria!!!” to rile them when people in-the-know will tell you “yeah, but the bacteria you find are the bacteria that are ALREADY IN YOUR MOUTH! You PUT them there when you drank from it!”

  3. I’d like to see this dude run out of bugs halfway through the month and then come out and make a statement about how secure OS X is. But, won’t happen. He’s looking for publicity.

    And maybe a new job.

  4. “For a total 284 days in 2006 (or more than nine months out of the year), exploit code for known, unpatched critical flaws in pre-IE7 versions of the browser was publicly available on the Internet. Likewise, there were at least 98 days last year in which no software fixes from Microsoft were available to fix IE flaws that criminals were actively using to steal personal and financial data from users… In contrast, Internet Explorer’s closest competitor in terms of market share — Mozilla’s Firefox browser — experienced a single period lasting just nine days last year in which exploit code for a serious security hole was posted online before Mozilla shipped a patch to remedy the problem.”

    Via slashdot http://it.slashdot.org/it/07/01/04/162238.shtml

  5. Bugs, bugs, bugs, bugs. What a mess(not)-but on the other hand we’re all still waiting breathlessly for that FIRST self-replicating virus. These guys should be focusing on what’s important. Instead they want to be idiots.

  6. Have you noticed that three of the bugs require a “working Ruby interpreter” and the other requires a “working Perl interpreter”.

    That’s probably why so many Mac users are not getting these so-called exploits to work. They don’t have Ruby and Perl installed.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.