CVE-2014-3166

N/A

Published: August 13, 2014 at 01:00 AM UTC

Updated: June 17, 2026 at 12:07 AM UTC

3 products affected across 2 vendorsDebian LinuxChromeAndroid· also runs on 4 platforms

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 2%

Description

The Public Key Pinning (PKP) implementation in Google Chrome before 36.0.1985.143 on Windows, OS X, and Linux, and before 36.0.1985.135 on Android, does not correctly consider the properties of SPDY connections, which allows remote attackers to obtain sensitive information by leveraging the use of multiple domain names.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

7.0 8.0

Chrome · Googlenpm

95%

v < 36.0.1985.135v < 36.0.1985.143v < 36.0.1985.57

Affected range stops below 36.0.1985.135, so it looks safe — our inference, not a vendor statement

Affected range stops below 36.0.1985.143, so it looks safe — our inference, not a vendor statement

Affected range stops below 36.0.1985.57, so it looks safe — our inference, not a vendor statement

apple-iphone-os (environment) · apple-macos (environment) · google-android (environment) · linux-linux-kernel (environment) · microsoft-windows (environment)

Android · Googledevice

80%

All versions