Red Hat Bugzilla – Bug 766865
CVE-2011-4607 putty: keyboard-interactive replies are not wiped from memory after authentication
Last modified: 2012-08-08 05:53:26 EDT
From the upstream advisory :
When PuTTY has sensitive data in memory and has no further need for it, it should wipe the data out of its memory, in case malware later gains access to the PuTTY process or the memory is swapped out to disk or written into a crash dump file. An obvious example of this is the password typed during SSH login; other examples include obsolete session keys, public-key passphrases, and the private halves of public keys.
PuTTY 0.59 to 0.61 inclusive had a bug in which they failed to wipe from memory the replies typed by the user during keyboard-interactive authentication. Since most modern SSH-2 servers use the keyboard-interactive method for password logins (rather than SSH-2's dedicated password method), this meant that those versions of PuTTY would store your login password in memory for as long as they were running.
PuTTY 0.62 fixes this bug. Keyboard-interactive responses, including passwords, are now correctly wiped from PuTTY's memory again.
However, it is still unavoidably very dangerous if malicious software is in a position to read the memory of your PuTTY processes: there is still a lot of sensitive data in there which cannot be wiped because it's still being used, e.g. session keys. If you're using public-key authentication and malware can read a Pageant process, that's even worse, because the decrypted private keys are stored in Pageant! This fix somewhat mitigates the risks, but no fix can eliminate them completely.
This affects putty releases 0.59 through and including 0.61, and is fixed in 0.62 via svn commit r9357 .
Created putty tracking bugs for this issue
Affects: fedora-all [bug 766867]
Affects: epel-5 [bug 766868]
Affects: epel-6 [bug 766869]
Is this something that should get a CVE? While removing sensitive information from memory when no longer needed is required by e.g. certain crypto processing standards, I can't think of an example when similar problem was handled as vulnerability that got CVE.
Not sure this is the best place to discuss this, perhaps oss-sec?
It's been assigned a CVE-2011-4607:
I think, however, that if it's possible to get keys/passphrases/etc. from memory due to a flaw in a program that didn't used to be there (remember, this was introduced in 0.59), then I think it deserves a CVE name. Obviously some protection was there before that was not there for a while, and is now back again.