Don't worry, it'll be all Reich! Googler saves Grammarly nazis from hacker invasion

Language tool maker scrambles to patch info leak

By Iain Thomson in San Francisco


Updated A critical flaw in the Chrome extension of Grammarly – the grammar-checking software with online ads second only to Geico in terms of their ability to annoy – has left all 22 million users' personal records available to all.

The vulnerability, spotted on February 2 by Google Project Zero's Tavis Ormandy – allows any website to access "documents, history, logs, and all other data" associated with grammar pedants' Grammarly accounts if they use the browser plugin and browse to a malicious webpage. Poor coding in the extension allows peeps' authentication tokens to be grabbed by four lines of code on those evil websites.

"I'm calling this a high severity bug, because it seems like a pretty severe violation of user expectations," Ormandy reported. "Users would not expect that visiting a website gives it permission to access documents or data they've typed into other websites."


As a result, any website that a Grammarly Chrome extension user visits could scrape up their authentication tokens, and then access every document, note, or keystroke the app has recorded. Ormandy notified the app makers, and gave them a 90-day countdown to fix it.

To its credit, Grammarly didn’t sit on its hands. The developers fixed the issue over the weekend and, as of Monday morning, have pushed out a fix to all users.

"Grammarly had fixed the issue and released an update to the Chrome Web Store within a few hours, a really impressive response time," Ormandy said on Monday. "I've verified that Mozilla now also has the update, so users should be auto-updated to the fixed version. I'm calling this issue fixed." ®

Updated to add

A spokesperson for the plugin maker has been in touch to say:

Grammarly resolved a security bug reported by Google’s Project Zero security researcher, Tavis Ormandy, within hours of its discovery. At this time, Grammarly has no evidence that any user information was compromised by this issue. We’re continuing to monitor actively for any unusual activity. The security issue potentially affected text saved in the Grammarly Editor. This bug did not affect the Grammarly Keyboard, the Grammarly Microsoft Office add-in, or any text typed on websites while using the Grammarly browser extension. The bug is fixed, and there is no action required by Grammarly users.

Sign up to our NewsletterGet IT in your inbox daily


More from The Register

Patch this run(DM)c Docker flaw or you be illin'... Tricky containers can root host boxes. It's like that – and that's the way it is

'Doomsday scenario' unless devops crowd walks this way

Stop us if you've heard this one: Remote code hijacking flaw in Apache Struts, patch ASAP

Advisory issued over yet another critical security vulnerability

At least Sony offered a t-shirt, says macOS flaw finder: Bug bounties now for Macs if you want this 0-day, Apple

Vid Cupertino's tight-wads called out by fella who found password, private key leak

Xen Project patches Intel’s Lazy FPU flaw, VMware doesn't need to

UPDATE Guest register states are readable, but the patch cavalry has arrived

Microsoft's Jet crash: Zero-day flaw drops after deadline passes

Updated Don't click on that dodgy link, people

The BMC in OpenBMC stands for 'Burglarize My Computer' – thanks to irritating security flaw

Pantsdown vulnerability affects various BMC stacks as well as OpenBMC on systems using two particular Aspeed chips

Intel Management Engine JTAG flaw proof-of-concept published

"God Mode" requires special USB debugging connector

So phar, so FUD: PHP flaw puts WordPress sites at risk of hacks

Bsides Manchester But claims of 'complete system compromise' are a little extreme

Patch alert! Easy-to-exploit flaw in Linux kernel rated 'high risk'

Urgent security triage needed

Latest Google+ flaw leads Chocolate Factory to shut down site early

52.5 million accounts at risk, tens of people are worried