CVE-2014-3166
published 2014-08-13CVE-2014-3166: 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…
PriorityP419medium4.3CVSS 2.0
AVNACMAuNCPINAN
EPSS
1.50%
71.7th percentile
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
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| chrome | < 36.0.1985.143 | 36.0.1985.143 | |
| chrome | < 36.0.1985.135 | 36.0.1985.135 | |
| chrome | < 36.0.1985.57 | 36.0.1985.57 |
CVSS provenance
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/A:N
osv7.5HIGH
vendor_ubuntu7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
Oxide vulnerabilities
vendor_ubuntu·2014-08-20·CVSS 7.5
CVE-2014-3165 [HIGH] Oxide vulnerabilities
Title: Oxide vulnerabilities
Summary: Several security issues were fixed in Oxide.
A use-after-free was discovered in the websockets implementation in Blink.
If a user were tricked in to opening a specially crafted website, an
attacker could potentially exploit this to cause a denial of service via
renderer crash. (CVE-2014-3165)
An issue was discovered in the Public Key Pinning implementation in
Chromium. An attacker could potentially exploit this to obtain sensitive
information. (CVE-2014-3166)
Multiple security issues were discovered in Chromium. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit these to cause a denial of service via application
crash or execute arbitrary code with the privileges of the user invoking
the program.
GHSA
GHSA-7mjp-hj3c-3vxc: The Public Key Pinning (PKP) implementation in Google Chrome before 36
ghsa_unreviewed·2022-05-14
CVE-2014-3166 [MEDIUM] CWE-200 GHSA-7mjp-hj3c-3vxc: The Public Key Pinning (PKP) implementation in Google Chrome before 36
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.
OSV
oxide-qt vulnerabilities
osv·2014-08-20·CVSS 7.5
CVE-2014-3165 [HIGH] oxide-qt vulnerabilities
oxide-qt vulnerabilities
A use-after-free was discovered in the websockets implementation in Blink.
If a user were tricked in to opening a specially crafted website, an
attacker could potentially exploit this to cause a denial of service via
renderer crash. (CVE-2014-3165)
An issue was discovered in the Public Key Pinning implementation in
Chromium. An attacker could potentially exploit this to obtain sensitive
information. (CVE-2014-3166)
Multiple security issues were discovered in Chromium. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit these to cause a denial of service via application
crash or execute arbitrary code with the privileges of the user invoking
the program. (CVE-2014-3167)
OSV
CVE-2014-3166: The Public Key Pinning (PKP) implementation in Google Chrome before 36
osv·2014-08-13·CVSS 4.3
CVE-2014-3166 [MEDIUM] CVE-2014-3166: The Public Key Pinning (PKP) implementation in Google Chrome before 36
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
http://googlechromereleases.blogspot.com/2014/08/chrome-for-android-update.htmlhttp://googlechromereleases.blogspot.com/2014/08/chrome-for-ios-update.htmlhttp://googlechromereleases.blogspot.com/2014/08/stable-channel-update.htmlhttp://secunia.com/advisories/59693http://secunia.com/advisories/59904http://secunia.com/advisories/60685http://secunia.com/advisories/60798http://security.gentoo.org/glsa/glsa-201408-16.xmlhttp://www.debian.org/security/2014/dsa-3039http://www.ietf.org/mail-archive/web/tls/current/msg13345.htmlhttp://www.securityfocus.com/bid/69202http://www.securitytracker.com/id/1030732https://code.google.com/p/chromium/issues/detail?id=398925https://src.chromium.org/viewvc/chrome?revision=286598&view=revisionhttps://src.chromium.org/viewvc/chrome?revision=288435&view=revisionhttp://googlechromereleases.blogspot.com/2014/08/chrome-for-android-update.htmlhttp://googlechromereleases.blogspot.com/2014/08/chrome-for-ios-update.htmlhttp://googlechromereleases.blogspot.com/2014/08/stable-channel-update.htmlhttp://secunia.com/advisories/59693http://secunia.com/advisories/59904http://secunia.com/advisories/60685http://secunia.com/advisories/60798http://security.gentoo.org/glsa/glsa-201408-16.xmlhttp://www.debian.org/security/2014/dsa-3039http://www.ietf.org/mail-archive/web/tls/current/msg13345.htmlhttp://www.securityfocus.com/bid/69202http://www.securitytracker.com/id/1030732https://code.google.com/p/chromium/issues/detail?id=398925https://src.chromium.org/viewvc/chrome?revision=286598&view=revisionhttps://src.chromium.org/viewvc/chrome?revision=288435&view=revision
2014-08-13
Published