First published: Fri Jul 09 2021(Updated: )
PuTTY through 0.75 proceeds with establishing an SSH session even if it has never sent a substantive authentication response. This makes it easier for an attacker-controlled SSH server to present a later spoofed authentication prompt (that the attacker can use to capture credential data, and use that data for purposes that are undesired by the client user).
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/putty | <=0.63-10+deb8u1<=0.75-2<=0.63-10 | 0.75-3 0.74-1+deb11u1 |
debian/putty | <=0.70-6<=0.74-1 | 0.74-1+deb11u1 0.78-2 0.78-2+deb12u1 0.80-1 |
PuTTY | <=0.75 |
https://git.tartarus.org/?p=simon/putty.git;a=commit;h=1dc5659aa62848f0aeb5de7bd3839fecc7debefa
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2021-36367.
The severity of CVE-2021-36367 is high (8.1).
PuTTY version 0.75 is affected by CVE-2021-36367.
CVE-2021-36367 allows for an attacker-controlled SSH server to present a spoofed authentication prompt and capture credential data.
Yes, you can find more information about CVE-2021-36367 in the references section.