Timeline for How can the OpenSSL CCS Injection vulnerability (CVE-2014-0224) be exploited?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jul 7, 2014 at 22:33 | history | suggested | user2428118 | CC BY-SA 3.0 |
Improved title
|
| Jul 7, 2014 at 22:23 | review | Suggested edits | |||
| S Jul 7, 2014 at 22:33 | |||||
| Jul 4, 2014 at 8:17 | history | tweeted | twitter.com/#!/StackSecurity/status/484974271547310080 | ||
| Jul 3, 2014 at 11:15 | vote | accept | TimC | ||
| Jul 3, 2014 at 11:07 | answer | added | aviv | timeline score: 6 | |
| Jul 3, 2014 at 10:41 | comment | added | dave_thompson_085 | I think that Q does answer your question, though briefly. AIUI (from discussion on the openssl maillist, not actually following the code) it doesn't downgrade the cipher the way you stated, instead it 'downgrades' the key by getting openssl to do the correct KDF on incorrect input: only the nonsecret nonces, but not the premaster secret as per spec. The attacker can re-do the KDF and get the session keys, and then Bob and Alice are your uncle and aunt as it were. | |
| Jul 3, 2014 at 9:49 | comment | added | TimC | I considered adding to that discussion, but I wouldn't consider my question a duplicate as it talks more about how this vulnerability works from a technical level | |
| Jul 3, 2014 at 9:47 | comment | added | user2428118 | See also security.stackexchange.com/q/60763/13154. Duplicate? | |
| Jul 3, 2014 at 9:37 | history | asked | TimC | CC BY-SA 3.0 |