eBay scammers work unpatched weaknesses in Firefox, IE
Other sites also vulnerable to CSS attack
Agentless Backup is Not a Myth
Updated eBay scammers have been exploiting unpatched weaknesses in the Firefox and Internet Explorer browsers to deliver counterfeit pages that try to dupe people surfing the online auction house to bid on fraudulent listings.
The attacks managed to inject eBay pages with hostile code by exploiting issues long known to afflict Firefox and IE. While eBay has managed to block the exploit from working on its domains, other websites that accept user-generated content may still be vulnerable to the attacks, web security experts warn.
Firefox security volunteers say they are in the process of patching the vulnerability. For their part, Microsoft officials say the exploits aren't the result of a vulnerability in IE but rather of websites that fail to properly protect against such attacks.
The evil genius behind the eBay scheme managed to pull off what amounts to an XSS, or cross-site scripting, attack that injected forbidden javascript elements stored on third-party websites. That allowed the eBay pages to contain outside email links and other unauthorized code while still evading toolbars designed to detect fraudulent listings.
In addition to injecting a link that automatically prompts users to email the seller at an aol.com address, the scam used a random number generator to change the item number each time the page was loaded. Item numbers are supposed to be unique and are used to report fraudulent listings. Changing the number made it harder for eBay's fraud busters to remove bogus auctions.

Picture perfect: an eBay listing with fraudulent elements injected into it
The attacks targeted Firefox by exploiting the way the browser implements what's known as XBL, or XML binding language. By invoking a rogue CSS, or cascade style sheet, hosted on a third-party site, the Mozilla browser was tricked into running forbidden code that injected fraudulent content into the listings. Over the past week, there has been considerable debate among Mozilla security volunteers about whether the condition amounted to a security vulnerability or an intended feature. They decided to make changes to the browser after witnessing the eBay scams that abused it.
"Patches are being constructed to get rid of an existing useful feature due to the patent inability of some websites to take elementary protective measures even after 5 years of the feature existing and after being repeatedly told to NOT link to external sheets by all browser vendors," one debate participant wrote El Reg in an email. "Note that the patch won't really help eBay much unless they really do start filtering the CSS they allow, since so much can be accomplished with just CSS."
A similar issue also related to off-site CSSes allowed the eBay attacks to work flawlessly on IE browsers, as the above screenshot makes clear. The exploit targeted IE functionality commonly referred to as expressions that has long been a known vector of XSS exploits. While IE 8 has been locked down to prevent such attacks, versions 6 and 7 of the Microsoft browser have not, and Bill Sisk, Microsoft's security response communications manager, said there are no plans to add such protections to the older browsers.
"Our investigation has shown that it is not a vulnerability in Internet Explorer," Sisk wrote in an email over the weekend. "In fact, the claim represents a method by which malicious attackers can exploit specific functionality in websites to bypass security measures. The nature of these attacks is not new and website operators commonly have protections in place to mitigate against such attacks."
Sisk's point is well-taken that eBay and other websites have an affirmative duty to filter code that allows these attacks to succeed. But his insistence that IE is blameless isn't entirely right, either. Microsoft has rightfully decided to protect IE 8 users by changing some of the browser's behavior concerning external CSS. Users of IE 7 deserve no less.
As was the case last week even large, sensitive sites such as eBay don't always protect against such attacks. Company spokeswoman Nichola Sharpe issued a statement that read in part: "This is not a new security threat, our online security experts are already aware of this and have identified it as a known bug in Firefox. eBay utilizes sophisticated security technologies to protect our customers against attacks such as this. We continually update our security to deal with emerging threats - and have done so with this threat."
Maybe, but eBay took more than 24 hours to remove one such fraudulent listing after it was reported, said Cefn Hoile, a browser security expert who first reported the Firefox issue.
"eBay has to take some responsibility for sure," Hoile wrote in an email. "They chose to serve this content which incorporated the third party stylesheet."
The only way to effectively protect users from such attacks is to white-list filter a set number of CSS functions deemed to be safe and to block everything else. That may be patently obvious to some, but if eBay has only now gotten around to implementing such measures, it's a good bet plenty of other websites are still wide open to this attack. Which means we wouldn't be surprised to see more attacks like these coming to a Web 2.0 site near you. ®
This article was updated to remove the words "bugs" and "vulnerabilities" to reflect Microsoft's contention that the attacks aren't the result of flaws in IE.
COMMENTS
All passing the buck!
I notice everyone mentioned in the article declares that they themselves are not at fault, when they are patently ALL at fault!
And Microsoft now comes in and has the article re-edited to its own whims?
That is outrageous!
Talking about IE bugs - I cannot update from IE6! And of course I cannot uninstall it either. That to me constitutes both a bug and a vulnerability.
@2 A.Cowards
==
@Wortel
By Anonymous Coward Posted Monday 9th March 2009 12:20 GMT
Flame
"you are sadly mistaking (sic) about the browser not being at fault"
What you mean is :
"I did something stupid and the browser didn't fix it for me! Wah!"
It is NOT the browser's fault that you have chosen to implement something which is inherently insecure. I sincerely hope you aren't a web developer, because I wouldn't want you working for me.
==
Thanks for proving my point with that reply.
As a side note I did not claim the browser should 'fix' anything, I said "Failing to validate the source is not done in today's world.".
An extension like NoScript allows the user a chance to validate the source before executing the content. This is a function that could be integrated into the browser itself, and would be a sane addition to the already in-place systems for checking the sources of remote images and cookies.
As for not wanting me working for you, i'm quite content not working for your kind of narrow-minded Neanderthals.
==
@Wortel the monkey
By Anonymous Coward Posted Tuesday 10th March 2009 08:47 GMT
here's your peanuts. CSS is not a plain text file, it is served as text/css. See, this is the problem we have people without a clue thinking they know what is going on, Wortel is one of them.
==
I suppose I should thank you for trying to poison me then, as I am allergic to peanuts.
While we are on the subject of ill-thought-through actions, let's address your reply.
A style sheet has been and always will be a plain text file. The only thing you assume correctly is that it is -served- as text/css, but it is still the same plain text file after being transferred to the client. We call that description, 'text/css', a MIME type. You'll find it in Apache's server configuration if you know where to look. You do know where to look, do you?.
You can easily reconfigure Apache to mark a different file as 'text/css' if you wanted. Do we do that? no, we don't. Do we want to? Maybe, in the future.
It doesn't process the file in any other way, that's the job of the web browser.
But I suppose you want to blame the webserver now for handing out style sheets? Go ahead.
In a way I should thank you, for the ignorance of your kind like previous AC keeps people like me whom apparently are "people without a clue thinking they know what is going on" employed, paid and happy. Well scratch the happy part, supporting trolls like yourself should be rewarded with the keys to the armoury.
@Wortel the monkey
here's your peanuts. CSS is not a plain text file, it is served as text/css. See, this is the problem we have people without a clue thinking they know what is going on, Wortel is one of them.

IT infrastructure monitoring strategies
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider
Data control in the cloud
Cloud based data management
Agentless Backup is Not a Myth