Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2013-4208: The rsa_verify function in PuTTY before 0.63 (1) does not clear sensitive process memory after use and (2) doe

16
Routine
LOW 2.1DOWNGRADEUPGRADE

CVE-2013-4208 is a low-severity flaw (CVSS 2.1) affecting putty, putty. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score2.1 (Low)
EPSS exploit chance0.4% (top 67%)
CISA exploited listNo
WeaknessCWE-200
Published2013-08-19
Last modified2026-06-16
Publisher (CNA): Red Hat, Inc. · Vendor: putty · simon tatham

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

putty putty DOWNGRADE
Affected: 0.45 · 0.46 · 0.47 · 0.48 · 0.49 · 0.50 · 0.51 · 0.52
Fixed in: no fixed release known
Safe to downgrade to: a release before 0.45
1. Check installed version
apt-cache policy putty || rpm -q putty || putty --version
2. No fixed release: DOWNGRADE to a release before 0.45 (Debian / Ubuntu)
apt-cache madison putty sudo apt install putty=<VERSION_BEFORE_0.45> sudo apt-mark hold putty
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list putty sudo dnf downgrade putty-<VERSION_BEFORE_0.45> sudo dnf versionlock add putty
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
simon tatham putty UPGRADE
Affected: <= 0.62 · 0.53
Fixed in: newer than 0.62
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy putty || rpm -q putty || putty --version
2. UPGRADE to newer than 0.62 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade putty
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade putty
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-4208?

putty: downgrade or apply the listed mitigation; putty: upgrade to newer than 0.62. Exact commands for each OS are on this page.

Is CVE-2013-4208 being exploited?

CVE-2013-4208 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-4208 affect?

CVE-2013-4208 affects putty, putty. Severity is low (CVSS 2.1). 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 k

How urgent is CVE-2013-4208?

Priority 16/100. No elevated risk signals yet.

Software pages

PuTTY vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.