First published: Mon Aug 19 2013(Updated: )
The rsa_verify function in PuTTY before 0.63 (1) does not clear sensitive process memory after use and (2) does not free certain structures containing sensitive process memory, which might allow local users to discover private RSA and DSA keys.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
PuTTY | =0.45 | |
PuTTY | =0.46 | |
PuTTY | =0.47 | |
PuTTY | =0.48 | |
PuTTY | =0.49 | |
PuTTY | =0.50 | |
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.53 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-4208 is classified as a high severity vulnerability due to the potential exposure of sensitive cryptographic keys.
To fix CVE-2013-4208, upgrade PuTTY to version 0.63 or later where the vulnerability has been addressed.
Local users running PuTTY versions prior to 0.63 are affected by CVE-2013-4208.
The risks associated with CVE-2013-4208 include potential unauthorized access to private RSA and DSA keys.
While upgrading is the recommended solution for CVE-2013-4208, minimizing local access can reduce the risk temporarily.