Yahoo! plugs leaky Axis extension

Powered by SC Magazine
 

Chrome plugin loses shine at launch.

Yahoo!'s Chrome search extension dubbed Axis was found on its debut launch to have exposed a private certificate capable of allowing attackers to craft authentic but malicious plugins.

The flaw was detected by Aussie security researcher and coder Nik Cubrilovic who detailed a proof of concept interception attack that used the signing key on his blog.

The certificate file is used by Yahoo! to sign the extension package, which is used by Chrome and the webstore to authenticate that the package comes from Yahoo!," Cubrilovic said.

"With access to the private certificate file, a malicious attacker is able to create a forged extension that Chrome will authenticate as being from Yahoo!

“The clearest implication is that with the private certificate file and a fake extension, you can create a spoofed package that captures all web traffic including passwords [and] session cookies."

He said the code could be delivered by running a DNS spoof of the update URL which would silently install and run the spoofed extension during an update.

Yahoo! disabled the Google Chrome extension and issued a fixed version.

Yahoo!'s Axis team blacklisted the exposed certificate key with Google which it said resolved the vulnerability.

“We take issues like this very seriously and are dedicated to working around the clock to ensure resolution. We apologise for any inconvenience.”

This article originally appeared at scmagazineuk.com

Copyright © SC Magazine, UK edition


Yahoo! plugs leaky Axis extension
 
 
 
Top Stories
NSW to build its own myGov
Service NSW digital profiles available by September.
 
Android bug leaves a billion phones open to attack
Hackers only need phone number to target devices.
 
Australia's leaders agree to end GST-free online goods
Gerry Harvey may finally get his way.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
Should law enforcement be able to buy and use exploits?



   |   View results
Yes
  13%
 
No
  51%
 
Only in special circumstances
  17%
 
Yes, but with more transparency
  19%
TOTAL VOTES: 714

Vote