Some advice to all antivirus makers that create their own "secure browsers": leave Chromium's security features alone!Īccessing this URL will tell you if you have a vulnerable version of the SafeZone browser installed on your PC.Īnd yet another case of forking Chromium for "security" because of your virus expertise. In SafeZone, attackers could also launch links that started with "file://" which is the URL naming scheme used to access local files. In Chromium, users would only be allowed to open links from the command line if the URL started with http, https, javascript, data, etc. This feature allowed only WebSafe URLs to be opened via command-line instructions (like the malicious ones sent to the open RPC endpoint). The Google researcher blamed this entire fiasco on Avast's decision to overwrite a security feature inside the default Chromium setup. The latest version of the Avast antivirus released on February 3 included a complete fix for this problem. Ormandy told Avast about their problem on December 18, and ten days later, the company issued a quick fix that prevented this issue from being exploited.
Users who purchased an antivirus to bolster their security are practically being delivered a live backdoor, no matter if they wanted it or not. This entire situation is extremely funny and tragic at the same time. If you have SafeZone installed on your PC, you're doomed, since the malicious link can be opened in other browsers and work regardless.
"This allows an attacker to read cookies, email, interact with online banking and so on." "Additionally, you can send arbitrary *authenticated* HTTP requests, and read the responses," Mr. Avast purposely disabled a Chromium security feature Ormandy noted, saying that bookmarks, preferences, passwords and cookies are automatically added to SafeZone without the user's consent. "Although this attack relies on Avastium (Avast's port of Chromium), the victim does *not* have to be using it, and never has to have used it, because your profile is automatically imported from Chrome on startup," Mr.
About avast safe zone code#
These commands could be bundled inside malicious JavaScript code that was executed locally on the user's computer, where localhost access would allow it to reach these open RPC endpoints, even if SafeZone was not actually running, and the malicious links were clicked inside another browser.Īn attacker wouldn't even need an info-stealing malware strain if they knew their target had Avast's SafeZone installed, a browser that was dumping everything out in the open. Users don't have to use the browser, only have it installedĪccording to the researcher's explanation, attackers could send malicious commands to an RPC endpoint that was left open in the browser's core engine.
About avast safe zone series#
Ormandy explains, this poor excuse of a browser was allowing a third-party to carry out a series of attacks, all by fooling a user into clicking a link, which is not really that hard if you hide it under a short URL. Just like Chromodo, SafeZone is built on top of Chromium, the open source browser project on which Google Chrome, Vivaldi, and Opera are based as well.Īs Mr.
About avast safe zone upgrade#
Antivirus makers should stick to antivirus softwareĬalled SafeZone and also known as Avastium, Avast's custom browser is offered as a bundled download for all those who purchase or upgrade to a paid version of Avast Antivirus 2016. While Chromodo was caught disabling a crucial security feature called Same Origin Policy (SOP), Avast's Chromium fork is much worse, bringing a series of problems, one of which allows attackers to list and read files from your computer after you click a simple malicious link. Just two days after Comodo's Chromodo browser was publicly shamed by Google Project Zero security researcher Tavis Ormandy, it's now Avast's turn to be scorned for failing to provide a "secure" browser for its users.
0 kommentar(er)
