Bug 766865 (CVE-2011-4607)
Summary: | CVE-2011-4607 putty: keyboard-interactive replies are not wiped from memory after authentication | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Vincent Danen <vdanen> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | fedora, jima, tremble |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | putty 0.62 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-10 10:58:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 766867, 766868, 766869 | ||
Bug Blocks: |
Description
Vincent Danen
2011-12-12 17:43:33 UTC
Created putty tracking bugs for this issue Affects: fedora-all [bug 766867] Affects: epel-5 [bug 766868] Affects: epel-6 [bug 766869] Is this something that should get a CVE? While removing sensitive information from memory when no longer needed is required by e.g. certain crypto processing standards, I can't think of an example when similar problem was handled as vulnerability that got CVE. Not sure this is the best place to discuss this, perhaps oss-sec? It's been assigned a CVE-2011-4607: http://seclists.org/oss-sec/2011/q4/500 I think, however, that if it's possible to get keys/passphrases/etc. from memory due to a flaw in a program that didn't used to be there (remember, this was introduced in 0.59), then I think it deserves a CVE name. Obviously some protection was there before that was not there for a while, and is now back again. This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products. |