![\"LastPass](\"\/huntsville-al\/wp-content\/uploads\/sites\/13\/2017\/03\/LastPass-Chrome-bug.png\")
<\/p>\nBy Catalin Cimpanu
\nMarch 22, 2017 05:28 AM 0
\nLastPass says it patched one of two separate bugs that affected its Chrome and Firefox browser extensions, which if exploited, would have allowed a third-party to extract passwords from users visiting a malicious website.<\/p>\n
Both bugs were discovered by Tavis Ormandy, a security researcher working for Google’s Project Zero.<\/p>\n
Of the two bugs Ormandy discovered, LastPass engineers patched only the one affecting the Chrome extension, while the one affecting the Firefox version is under investigation.<\/p>\n
Bug in LastPass Chrome extension
\nThe vulnerability affecting the LastPass Chrome extension can be exploited by attacking an intermediary JS script that stands between the user’s browser and the LastPass cloud service, where the company stores user passwords.<\/p>\n
“It’s possible to proxy untrusted messages to LastPass 4.1.42 due to a bug, allowing websites to access internal privileged RPCs (Remote Procedure Calls). ” Ormandy explained. “There are a lot of RPCs, allowing complete control of the LastPass extension, including stealing passwords. If you have the ‘Binary Component’ installed, this even allows arbitrary code execution.”<\/p>\n
Ormandy put together proof-of-concept code that executes code on a user’s machine via this intermediary script and launches an instance of the Windows Calculator. All OS platforms are affected, not just Chrome on Windows.<\/p>\n
<\/p>\n
This PoC code can be altered to steal user passwords before they are copied and filled inside username and password fields.<\/p>\n
LastPass users are exposed to simple attack vectors, as attackers can host the weaponized code as a regular JS script on a website.<\/p>\n
On Twitter, LastPass said they already fixed the issue reported by Ormandy in the Chrome extension and promised a blog post with more details in the following days.<\/p>\n
Bug in LastPass Firefox extension
\nThe second bug Ormandy discovered affects LastPass’s Firefox add-on version 3.3.2 only. LastPass told Ormandy that version 3.3.2 is their most popular version.<\/p>\n
Despite this, two weeks ago, LastPass announced they were retiring the LastPass Firefox add-on v3.3.2 because of Firefox’s future plans to drop the old Add-ons API and move to a new system they call WebExtensions.<\/p>\n
The LastPass Chrome and Firefox extensions don’t use the same version numbers, and the v3 on Firefox is the stable branch.<\/p>\n
Ormandy didn’t provide details about how this bug works, but said that attackers can steal user credentials from LastPass password vaults using a similar Web-based exploit that relies on attackers luring users to a malicious website. The researcher also confirmed the issue was not resolved.<\/p>\n
More details are expected to become available in this bug report after LastPass fixes the vulnerability.<\/p>\n
![\"LastPass](\"https:\/\/www.technology-solved.com\/huntsville-al\/wp-content\/uploads\/sites\/13\/2017\/03\/LastPass-Firefox-bug.jpg\")
<\/p>\n
In July 2016, Ormandy found a similar bug that allowed attackers to extract passwords from LastPass. On the same day, Mathias Karlsson of Detectify found and disclosed a different issue, wich also led to a full password compromise.<\/p>\n
In April 2016, Malwarebytes found a fake LastPass Chrome extension offered via the official Google Web Store.<\/p>\n
In January 2016, security researcher Sean Cassidy developed a simple attack to collect LastPass master passwords.<\/p>\n
Any of these vulnerabilities should not keep users from installing a password manager, as this tweet wisely points out.<\/p>\n","protected":false},"excerpt":{"rendered":"
By Catalin Cimpanu March 22, 2017 05:28 AM 0 LastPass says it patched one of two separate bugs that affected its Chrome and Firefox browser extensions, which if exploited, would have allowed a third-party to extract passwords from users visiting a malicious website. Both bugs were discovered by Tavis Ormandy, a security researcher working for […]<\/p>\n","protected":false},"author":15,"featured_media":1930,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1066","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"acf":[],"yoast_head":"\n