E-mail address spoofing with RLOMay 24, 2011
When we reply to an e-mail, the address we see in the To-field serves a purpose beyond getting our answer back to original sender. We attach a meaning to these addresses. If we see
firstname.lastname@example.org, we expect that we're really sending a mail to someone at the Example company.
We may have learned not to trust the "From" address: that's about as unreliable as the return address on the back of an envelope. But we should be careful with what we think we see in To-field too.
The problem comes from the unicode "right-to-left override" (RLO, U+202E) character. It's an invisible character, that forces the text after it to be treated as right-to-left. For example
abc[RLO]def is displayed as
abcfed. It's well known that these kind of characters have security implications, it has led to other problems before, and this is a new one in that category:
It can be abused to display an E-mail address backwards, so that it appear to be on a different domain than it actually is.
An RLO is usually not accepted in an address, but it is accepted in the display name. The display name and the address are often shown together, allowing the RLO in the display name to affect how the address is shown. For example, "
Firstname Lastname [RLO] <email@example.com>" is displayed as "
Firstname Lastname <firstname.lastname@example.org> ".
This can not be used to spoof arbitrary addresses because the attacker's reversed real domain is still in it. But it can be used to spoof any domain. And a well chosen domain name reversed can look like a convincing foreign real name in the first part of the address.
This problem is worse than spoofing of the From-addresses, because an attacker can have a whole conversation without an indication to the victim that he's not who (from the domain) he pretends to be.
This affects most e-mail clients. These are the ones I tested, and whose vendors have been made aware of this in 2009.
still vulnerablefixed in June 2011 as part of new anti-phishing measures
- Hotmail: Fixed in February 2010
- Outlook 2007 (and later?): no fix announced, presumably still vulnerable
- Outlook Web Access: no fix announced, presumably still vulnerable
- Evolution: still vulnerable (Bug 601172)
- KMail: Fixed since December 2009, KDE 4.2.x (never released), 4.3.5 and 4.4.0
- And more...
On popular demand, here's some help to reproduce this.
If you like editing raw mail messages, here's an example From-header with an encoded RLO in it:
From: =?UTF-8?B?TW9jIExpYW1nIOKAriA=?= <email@example.com>
And here is the RLO character itself, as
abc[RLO]def. You should be able to copy-paste that in the settings of your email client (at the end of your real name). Selecting this text may act unusual; that's normal and correct behaviour: