A security weakness in a standard for handling special character sets in domain names could let an attacker spoof Web sites on non-Microsoft browsers, a researcher has warned.
The problem arises because certain browsers support a standardised way of representing domain names in the letters or characters of any language, security expert Eric Johanson said at the ShmooCon hacker convention this weekend. Called Internationalised Domain Names, the standard allows companies to register domain names that appear to be the same in different languages.
That encoding scheme could enable an attacker to create a fake Web site for a phishing scam. A spoofed link would seem to be a legitimate URL in the address bar of affected browsers -- Opera, Apple's Safari, and the Mozilla and Firefox browsers from the Mozilla Foundation. But instead of taking the victim to the trusted site, the link would lead to a phoney Web site with a domain rendered as the same address under the IDN process.
The Mozilla Foundation is looking for a long-term solution to the issue, Chris Hofmann, director of engineering at the company, said in a statement.
"With the increase in phishing attacks, there is a growing concern that exploits could take advantage of this feature to trick users into visiting rogue sites," Hofmann stated. "Mozilla is looking at options for fixing or disabling this feature and should have more information available very soon."
Phishing attacks, which try to fool consumers into handing over sensitive information by creating legitimate-looking Web sites and email messages, have become a central security concern recently. While vulnerabilities in Microsoft's Internet Explorer have been the focus of much of the concern, other browsers also have had their fair share of flaws.
The security weakness in the IDN scheme comes as registrars push for support for expressing domain names in different languages and scripts.
"There are now many ways to display any domain name on a browser, as there are a huge number of (character sets) which look very similar to Latin (characters)," Johanson said in an advisory.
The advisory demonstrates the attack using the domain for PayPal, but using an alternate Unicode character for the first "a". That gives an address that looks like "http://www.pàypal.com," but with a smaller "a."
Details of the flaw were shown at ShmooCon, a hacking and computer security convention, in Washington D.C., last weekend. The Shmoo Group, a loose association of security professionals that runs the convention, notified the affected browser makers in mid-January. Johanson is a member of the Shmoo Group.
Apple, VeriSign and Opera Software could not immediately be reached for comment.
Microsoft has not implemented support for IDN yet, so its IE browser is not vulnerable to the flaw.
Browser security is gaining attention among software makers. In December, Internet security company Netcraft released an IE plug-in that it said could help people avoid becoming victims of online fraud. In addition, Netscape announced last month that it is getting ready to release a browser designed to resist phishing attacks.
Talkback
Is that really a security flaw, or is it just the way things are supposed to be and people should look out for people exploiting legitimate domain names by registering domains with similar sounding names, I can't see any difference between, say päypal.com and paypals.com, both are obviously not paypal.com and would take you to the wrong site if you didn't read the name properly.
It is nice finally being able to go to web sites which have the "proper" spelling (E.g. müller and not mueller).
I would class this as a risk, but not a flaw, from the article, the system appears to work as it should, just people can exploit native English speakers ignorance of foriegn languages.
It looks more like a user education problem than a flaw, or have I misread something in the article?
Maybe the flaw is more in the registering process, surely a domain name like päypal,com, Yahooo.com or Yahoö.com should start ringing alarm bells with the registrars?
So, not a bug in the browsers but another thing IE lacks. I completely agree with David. The registrars need to take more responsilbility for the names they give out.
There are a number of fixes out there for this issue which have been created since the news came to pass -- this extension is among them.
http://tinyurl.com/4yd4n
One of the biggest arguments out there against IDN is the Phishing argument. This has now largely been negated by ICANN banning registeration of mixed character scripts that are likely to cause confusion.
However, another side of the story has been put. It is clear that many words in local characters have multiple representations when transliterated, often with more than one system, into Latin Characters. Each of these ambiguities offers an opportunity for a Phisher to conduct his Scam. Unlike the problem of eliminating the use of rogue cyrillics in Latin scripts, I see no easy solution to this problem, as each of the transliterations are in a single script and therefore legitimate. Indeed, each could have legitimate usuage, but surely often won't.
The argument therefore develops into the imperative of introducing IDN to prevent Phishing Scams in Asia. Without IDN, it is likely that the confusion over how to transliterate will result in a Pandemic of Scamming, the scale of which will be unprecidented! I feel that we should no longer be silent on the issue of Phishing as IDN undoubtedly will hold the moral high ground on this issue.