Description
Google Chrome before 19.0.1084.46 does not use a dedicated process for the loading of links found on an internal page, which might allow attackers to bypass intended sandbox restrictions via a crafted page.
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.
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Tumbleweed | chromium | 55.0.2883.75-3.1 | openSUSE-SU-2024:12948-1, openSUSE-SU-2024:10171-1 |
Advisories 2
- openSUSE-SU-2024:10171-1 chromedriver-55.0.2883.75-3.1 on GA media SUSE / openSUSE Security Updates · Feb 4, 2026
- openSUSE-SU-2024:12948-1 ungoogled-chromium-113.0.5672.92-1.1 on GA media SUSE / openSUSE Security Updates · Feb 4, 2026
References
- GLSA-201205-03 vendor-advisory
- google-chrome-links-sec-bypass(75589) vdb-entry
- openSUSE-SU-2012:0656 vendor-advisory
- 1027067 vdb-entry
- http://code.google.com/p/chromium/issues/detail?id=113496
- http://googlechromereleases.blogspot.com/2012/05/stable-channel-update.html
- 53540 vdb-entry
- openSUSE-SU-2012:0993 vendor-advisory
- oval:org.mitre.oval:def:15223 vdb-entry signature