Google Chrome 36.0.1985.142 PKP sensitive information leak

2014.08.13

Credit: rch

Risk: Medium

Local: No

Remote: Yes

CVE: CVE-2014-3166

CWE: CWE-200

CVSS Base Score: 5/10

Impact Subscore: 2.9/10

Exploitability Subscore: 10/10

Exploit range: Remote

Attack complexity: Low

Authentication: No required

Confidentiality impact: Partial

Integrity impact: None

Availability impact: None

Centralize the logic for checking public key pins from ClientSocketNSS
and ProofVerifierChromium to TransportSecurityState::CheckPublicKeyPins.
This required adding an is_issued_by_known_root argument to this method.
In addition, CheckPublicKeyPins now only checks static pins if the
TransportSecurityState's enable_static_pins_ member is true. This defaults
to true only for official desktop builds. This also means that dynamic
pins are now checked on mobile and on non-official builds.
BUG=398925,391033
Review URL: https://codereview.chromium.org/433123003
Diff:
https://src.chromium.org/viewvc/chrome?revision=288435&view=revision

References:

https://src.chromium.org/viewvc/chrome?revision=288435&view=revision

https://code.google.com/p/chromium/issues/detail?id=398925

http://www.ietf.org/mail-archive/web/tls/current/msg13345.html

http://googlechromereleases.blogspot.com/2014/08/stable-channel-update.html

http://googlechromereleases.blogspot.com/2014/08/chrome-for-android-update.html

See this note in RAW Version

Vote for this issue:

50%

Thanks for you vote!

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.

Nick (*)

Email (*)

Video

Text (*)

(*) - required fields.

{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1

{{ x.comment }}

Google Chrome 36.0.1985.142 PKP sensitive information leak

References:

Thanks for you vote!

Thanks for you comment!Your message is in quarantine 48 hours.

Thanks for you comment!
Your message is in quarantine 48 hours.