2.1
CWE
200
Advisory Published
Updated

CVE-2013-4208: Infoleak

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 SoftwareAffected VersionHow 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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2013-4208?

    CVE-2013-4208 is classified as a high severity vulnerability due to the potential exposure of sensitive cryptographic keys.

  • How do I fix CVE-2013-4208?

    To fix CVE-2013-4208, upgrade PuTTY to version 0.63 or later where the vulnerability has been addressed.

  • Who is affected by CVE-2013-4208?

    Local users running PuTTY versions prior to 0.63 are affected by CVE-2013-4208.

  • What are the risks associated with CVE-2013-4208?

    The risks associated with CVE-2013-4208 include potential unauthorized access to private RSA and DSA keys.

  • Is there a workaround for CVE-2013-4208?

    While upgrading is the recommended solution for CVE-2013-4208, minimizing local access can reduce the risk temporarily.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203