For those confused about "where the bug lies"... It is a two-edged sword. The root-cause is in a cross-site scripting vulnerability on MySpace's website. This is then exploited by a "feature" that can be abused in Quicktime.
Honestly, I'm regurgitating a lot of that, and I'd certainly like to know someone who has actually developed using quicktime before and has used the HREF track feature that is in question. But this is certainly not all Apple's fault like MySpace seems to be indicating. If MySpace doesn't address the root cause of the problem, they are going to get more of these attacks.
+1 for Apple's security reputation (which it could use after last month)
-5 for MySpace's security reputation
For those confused about "where the bug lies"... It is a two-edged sword. The root-cause is in a cross-site scripting vulnerability on MySpace's website. This is then exploited by a "feature" that can be abused in Quicktime.
Macrumors said:We have devised a way to disable this QuickTime feature for those who use Internet Explorer.
It is a bug in Quicktime, not in IE. And given that it's a Javascript exploit, it can conceivably be used to target other browsers as well. I imagine that the active exploit is targeting an IE vulnerability, which is why that's what they've worked around.
There's no real detail in that report, though. It just says "there's a flaw, it involves Quicktime's Javascript support, we're working on it".
Not... well it is client side but the script isn't in the QT movie. All QuickTime can do is call a javascript function of the page it is hosted in. Note that QT can provide data to the javascript functions it calls (which makes sense).What exactly does it mean for a *website* to have a cross-scripting vulnerability? The javascript in QT is client side, is it not?
I haven't see a good description of exactly what happens in this exploit but it sounds like that when a user visits a web-page with crafted QT movie and views that movie it either brings up a another page that shows a fake myspace login page and/or it calls a javascript function found in the hosting web-page. If the later then the hosting web-page would be a myspace page and hence could be using myspace javascript code against itself.So if there is a JScript vulnerability, doesn't it have to occur at the browser level? Or does the JScript somehow make a request of MySpace's web server that gets bounced to an outside server by MySpace, which should not be allowed?
I'd like to know if it's technically a feature of QuickTime, a vulnerability of QuickTime, or a bug in QuickTime. The choice might involve semantics, but it's also a technical distinction.
Is a feature being removed?
This is potentially much more harmful to Apple from a PR standpoint than last week's Nike+iPod "stalking" story. Let's see what the press does with this one.
Saw that story in the Metro today, it didn't mention the distance thing though, also apparently you need to spend £150 to get the scanner for the Nike+iPod thing, last time I looked eyes were free, and can see further too.
That is why Nike is recommending that all users of Nike shoes disable their walking and running features so they can avoid being followed or otherwise tracked in public.Of course, there's also the age-old "following" hack that impacts all users of Nike shoes.![]()
Is it wrong of me to get a good chuckle from this story?![]()
You mean NewsCorp?
Yeah, Rupert Murdoch has a long history of Nigerian Bank Account schemes...
Windows is the most popular OS and nearly every post here slams it. Mac users just don't like MySpace for some reason. Social networking sites are cool; I had a profile on Xanga and later moved over to Facebook.It is probably one of the most popular sites on the internet yet nearly every post here slams it.
Windows is the most popular OS and nearly every post here slams it. Mac users just don't like MySpace for some reason. Social networking sites are cool; I had a profile on Xanga and later moved over to Facebook.![]()
It is a bug in Quicktime, not in IE. And given that it's a Javascript exploit, it can conceivably be used to target other browsers as well. I imagine that the active exploit is targeting an IE vulnerability, which is why that's what they've worked around.
There's no real detail in that report, though. It just says "there's a flaw, it involves Quicktime's Javascript support, we're working on it".