Re:Roaming through the OpenSSH client: CVE-2016-0777 and 0778
by drostie on Thursday January 14, 2016 @03:46PM
(#10904341)
The most interesting part of this disclosure is:
Basically the exploit reveals a big chunk of memory where, very often, your private keys happen to live. The memory has been freed, but on BSD systems the memory that was freed has not been zeroed in any way, so you still see the private keys.
[ Parent
| on HN ]
Re:Roaming through the OpenSSH client: CVE-2016-0777 and 0778
by abstractbeliefs on Thursday January 14, 2016 @03:52PM
(#10904393)
So basically, the end result is that we have heartbleed for SSH?
While the cause is slightly different, the ultimate effect is an attacker being able to read significant chunks of memory remotely, which for SSH often means private key details.
Re:Roaming through the OpenSSH client: CVE-2016-0777 and 0778
by drostie on Thursday January 14, 2016 @04:19PM
(#10904563)
Not quite. With apologies to Missy Elliott:
It needs the client, to be served it.
It's Heartbleed if you flip it and reverse it.
[.ti esrever dna ti pilf uoy fi deelbtraeH s'tI]
[.ti esrever dna ti pilf uoy fi deelbtraeH s'tI]
If you SSH in, we can search it
And if you're roaming, steal your private key bits
[.ti esrever dna ti pilf uoy fi deelbtraeH s'tI]
[.ti esrever dna ti pilf uoy fi deelbtraeH s'tI]
B, B, on BSD
or any platform with a bad libc
[Why-thai,-thai-o-toy-o-thai-thai]
[Why-thai,-thai-o-toy-o-thai-thai]
'Cause, they, don't zero bits,
Not that anyone expected it.
'Aint no shame, Libc, do your thang,
OpenSSH's do-nothing feature here is to blame.