Description
Google Chrome before 18.0.1025.142 does not properly check X.509 certificates before use of a SPDY proxy, which might allow man-in-the-middle attackers to spoof servers or obtain sensitive information via a crafted certificate.
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
- 1026877 vdb-entry
- chrome-spdy-sec-bypass(74411) vdb-entry
- 48618 third-party-advisory
- 48691 third-party-advisory
- 80739 vdb-entry
- oval:org.mitre.oval:def:14849 vdb-entry signature
- http://googlechromereleases.blogspot.com/2012/03/stable-channel-release-and-beta-channel.html
- 52762 vdb-entry
- http://code.google.com/p/chromium/issues/detail?id=116398
- 48763 third-party-advisory