Google patches Gmail message-forwarding flaw

Powered by SC Magazine
 

Google has patched a cross-site request forgery vulnerability in Gmail that could allow the forwarding of messages to a malicious user.

Researcher Petko Petkov of Gnucitizen said Sunday on his organisation's blog that Google had fixed the flaw.

Petkov told SCMagazineUS.com today that Google said no end-users were targeted via the flaw.

“According to them, no users were affected, mainly because no additional details on the issue were released before the fix,” he said.

Petkov released proof-of-concept code for the flaw on Sunday. Last week, he warned other researchers not to disclose details of the issue until Google fixes it, saying the vulnerability is “extremely nasty if you ask me.”

Petkov last week noted that, in the event of an attack, messages would continue to be forwarded to an attacker despite a fix because the filter, created by an exploit, is still present.

Last month, Petkov discovered a flaw in QuickTime and Firefox, as well as a vulnerability in Adobe Reader. Both flaws were quickly fixed by vendors last week.

A representative from the Mountain View, Calif.-based search giant could not be immediately reached for comment today.

US-CERT warned in an advisory updated on Monday that the flaw “may allow a request from an attacker to be interpreted as originating from an authenticated user,” and noted Google's fix.

See original article on SC Magazine US

Copyright © SC Magazine, US edition


Google patches Gmail message-forwarding flaw
 
 
 
Top Stories
Earning the right to innovate
Breaking down the barriers to innovation is a long, but rewarding process, says Bank of Queensland Group CIO, Julie Bale.
 
A call for timely reporting
[Blog post] Businesses need incentives to keep customer data secure.
 
Doubts cast on Queensland's ICT Dashboard
Opposition, former Govt CIO say it can't be trusted.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
What is delaying adoption of public cloud in your organisation?







   |   View results
Lock-in concerns
  26%
 
Application integration concerns
  3%
 
Security and compliance concerns
  29%
 
Unreliable network infrastructure
  9%
 
Data sovereignty concerns
  22%
 
Lack of stakeholder support
  3%
 
Protecting on-premise IT jobs
  5%
 
Difficulty transitioning CapEx budget into OpEx
  3%
TOTAL VOTES: 846

Vote