SoylentNews

Arthur T Knackerbracket [soylentnews.org] writes:

Story automatically generated by StoryBot Version 0.1.0a (Development).

Note: This is the complete story and will need further editing. It may also be covered by Copyright and thus should be acknowledged and quoted rather than printed in its entirety.

FeedSource: [SecurityWeek] collected from rss-bot logs

Time: 2016-08-17 08:05:05-17:00 UTC

Original URL: http://www.securityweek.com/address-bar-spoofing-vulnerability-found-several-browsers [securityweek.com]

Title: Address Bar Spoofing Vulnerability Found in Several Browsers

Suggested Topics by Probability (Experimental) : 19.4 science 19.4 OS 8.3 mobile 8.3 hardware 8.3 digiliberty 8.3 business 5.6 security 5.6 code 2.8 techonomics 2.8 technomics 2.8 software 2.8 careersedu 2.8 careers 2.8 breaking

--- --- --- --- --- --- --- Entire Story Below --- --- --- --- --- --- ---

Address Bar Spoofing Vulnerability Found in Several Browsers

Arthur T Knackerbracket has found the following story [securityweek.com]:

Chrome, Firefox and other web browsers are plagued by vulnerabilities that can be exploited to spoof their address bar. Some of the affected vendors are still working on addressing the issues.

Pakistan-based researcher Rafay Baloch discovered that the address bar in Google Chrome, also known as the omnibox, can be tricked into flipping URLs.

The problem, which affects Chrome for Android, is related to how Arabic and Hebrew text is written from right to left (RTL). If an attacker's URL starts with an IP address and it contains an Arabic character, the URL's host and path are reversed.

For example, the URL 127.0.0.1/ا/http://example.com becomes http://example.com/‭ا/127.0.0.1 as it contains the "ا" character, the Arabic letter alef, which causes the URL to be rendered RTL. The method works with other Arabic characters as well, as long as they are the rightmost "strong" character – the numbers and the dots in the IP address are considered "weak" characters.

"The IP address part can be easily hided specially on mobile browsers by selecting a long URL (google.com/fakepath/fakepath/fakepath/... /127.0.0.1) in order to make the attack look more realistic," Baloch explained in a blog post [rafayhackingarticles.net]. "In order to make the attack more realistic unicode version of padlock can be used in order to demonstrate the presence of SSL."

A similar vulnerability was also found in Firefox for Android (CVE-2016-5267 [mozilla.org]). However, in Firefox's case, the URL does not need to start with an IP address – the only requirement is that it contains Arabic characters that cause the URL to flip. For instance, http://عربي.امارات/google.com/test/test/test becomes google.com/test/test/test/عربي.امارات.

Google has known about this issue [chromium.org] for more than a year. Baloch said he informed Google about its presence in the Android version of Chrome in May, and the company addressed it in late June. Mozilla patched the flaw in Firefox for Android on August 2.

Baloch told SecurityWeek that other browsers are affected as well, including desktop versions. In the case of Firefox and Chrome, the vulnerability only impacts the mobile versions.

The researcher has earned $3,000 from Google, $1,000 from Mozilla and $1,000 from an unnamed browser vendor that is currently working on fixing the bug.

Original Submission