First published: Fri Mar 27 2015(Updated: )
The (1) ssh2_load_userkey and (2) ssh2_save_userkey functions in PuTTY 0.51 through 0.63 do not properly wipe SSH-2 private keys from memory, which allows local users to obtain sensitive information by reading the memory.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Debian | =7.0 | |
Fedora | =20 | |
Fedora | =22 | |
SUSE Linux | =13.1 | |
SUSE Linux | =13.2 | |
PuTTY | =0.51 | |
PuTTY | =0.52 | |
PuTTY | =0.53b | |
PuTTY | =0.54 | |
PuTTY | =0.55 | |
PuTTY | =0.56 | |
PuTTY | =0.57 | |
PuTTY | =0.58 | |
PuTTY | =0.59 | |
PuTTY | =0.60 | |
PuTTY | =0.61 | |
PuTTY | =0.62 | |
PuTTY | =0.63 | |
PuTTY | =0.53 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-2157 has a medium severity level due to its potential to expose sensitive information from memory.
To fix CVE-2015-2157, upgrade PuTTY to a version later than 0.63 that addresses the memory wiping issue.
PuTTY versions from 0.51 to 0.63 are affected by CVE-2015-2157.
Yes, local users can exploit CVE-2015-2157 to read sensitive SSH-2 private keys from memory.
CVE-2015-2157 affects multiple operating systems, including Debian and Fedora, using vulnerable versions of PuTTY.