CVE-2011-4607 json
PuTTY 0.59 through 0.61 does not clear sensitive process memory when managing user replies that occur during keyboard-interactive authentic…
published 2013-08-23 13 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4531
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
PuTTY 0.59 through 0.61 does not clear sensitive process memory when managing user replies that occur during keyboard-interactive authentication, which might allow local users to read login passwords by obtaining access to the process' memory.
Patch / fix
- putty Debian 14, Debian 13, Debian 12 0.62-1
debian advisories DEBIAN-CVE-2011-4607
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-4607 updated cvss 3.3
putty: keyboard-interactive replies are not wiped from memory after authentication
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
chiark.greenend.org.uk
/~sgtatham/putty/wishlist/password-not-wiped.html
vendor-advisory
-
seclists.org
/oss-sec/2011/q4/500
mailing-list
-
seclists.org
/oss-sec/2011/q4/499
mailing-list
Sources
- CVE List CVE-2011-4607
- NVD CVE-2011-4607
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.