Description
Google Chrome before 28.0.1500.71 does not properly determine the circumstances in which a renderer process can be considered a trusted process for sign-in and subsequent sync operations, which makes it easier for remote attackers to conduct phishing attacks via a crafted web site.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 7 | chromium-browser | 28.0.1500.71-1~deb7u1 | DSA-2724-1 |
Advisories 1
- DSA-2724-1 chromium-browser - several Debian Security (DSA / DLA) · Mar 9, 2026
References
- http://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=8a8eb83276778c9fbcf9ebcd4436077269b73074
- https://code.google.com/p/chromium/issues/detail?id=252062
- DSA-2724 vendor-advisory
- http://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=f0aa298677a1afb9a40b36e32bc9c4d9b4861eac
- oval:org.mitre.oval:def:17177 vdb-entry signature
- http://googlechromereleases.blogspot.com/2013/07/stable-channel-update.html