VuXML ID | Description |
46e1ece5-48bd-11e9-9c40-080027ac955c | PuTTY -- security fixes in new release
The PuTTY team reports:
New in 0.71:
- Security fixes found by an EU-funded bug bounty programme:
- + a remotely triggerable memory overwrite in RSA key exchange, which can occur before host key verification
- + potential recycling of random numbers used in cryptography
- + on Unix, remotely triggerable buffer overflow in any kind of server-to-client forwarding
- + multiple denial-of-service attacks that can be triggered by writing to the terminal
- Other security enhancements: major rewrite of the crypto code to remove cache and timing side channels.
- User interface changes to protect against fake authentication prompts from a malicious server.
Discovery 2019-03-16 Entry 2019-03-17 putty
< 0.71
putty-gtk2
< 0.71
putty-nogtk
< 0.71
https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html
|
5914705c-ab03-11e9-a4f9-080027ac955c | PuTTY 0.72 -- buffer overflow in SSH-1 and integer overflow in SSH client
Simon Tatham reports:
Vulnerabilities fixed in this release include:
- A malicious SSH-1 server could trigger a buffer overrun by sending
extremely short RSA keys, or certain bad packet length fields.
Either of these could happen before host key verification, so even
if you trust the server you *intended* to connect to, you would
still be at risk.
(However, the SSH-1 protocol is obsolete, and recent versions of
PuTTY do not try it by default, so you are only at risk if you work
with old servers and have explicitly configured SSH-1.)
- If a malicious process found a way to impersonate Pageant, then it
could cause an integer overflow in any of the SSH client tools
(PuTTY, Plink, PSCP, PSFTP) which accessed the malicious Pageant.
Other security-related bug fixes include:
- The 'trust sigil' system introduced in PuTTY 0.71 to protect
against server spoofing attacks had multiple bugs. Trust sigils
were not turned off after login in the SSH-1 and Rlogin protocols,
and not turned back on if you used the Restart Session command.
Both are now fixed.
Discovery 2019-07-14 Entry 2019-07-20 putty
< 0.72
putty-gtk2
< 0.72
putty-nogtk
< 0.72
https://lists.tartarus.org/pipermail/putty-announce/2019/000028.html
|
6190c0cd-b945-11ea-9401-2dcf562daa69 | PuTTY -- Release 0.74 fixes two security vulnerabilities
Simon Tatham reports:
[Release 0.74] fixes the following security issues:
- New configuration option to disable PuTTY's default policy of
changing its host key algorithm preferences to prefer keys it
already knows. (There is a theoretical information leak in this
policy.) [CVE-2020-14002]
- In some situations an SSH server could cause PuTTY to access freed
mdmory by pretending to accept an SSH key and then refusing the
actual signature. It can only happen if you're using an SSH agent.
Discovery 2020-06-27 Entry 2020-06-28 putty
< 0.74
putty-gtk2
< 0.74
putty-nogtk
< 0.74
https://lists.tartarus.org/pipermail/putty-announce/2020/000030.html
https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-dynamic-hostkey-info-leak.html
https://www.fzi.de/en/news/news/detail-en/artikel/fsa-2020-2-ausnutzung-eines-informationslecks-fuer-gezielte-mitm-angriffe-auf-ssh-clients/
CVE-2020-14002
https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-agent-keylist-used-after-free.html
|
9b973e97-0a99-11e7-ace7-080027ef73ec | PuTTY -- integer overflow permits memory overwrite by forwarded ssh-agent connections
Simon G. Tatham reports:
Many versions of PuTTY prior to 0.68 have a heap-corrupting integer
overflow bug in the ssh_agent_channel_data function which processes
messages sent by remote SSH clients to a forwarded agent connection. [...]
This bug is only exploitable at all if you have enabled SSH
agent forwarding, which is turned off by default. Moreover, an
attacker able to exploit this bug would have to have already be able
to connect to the Unix-domain socket representing the forwarded
agent connection. Since any attacker with that capability would
necessarily already be able to generate signatures with your agent's
stored private keys, you should in normal circumstances be defended
against this vulnerability by the same precautions you and your
operating system were already taking to prevent untrusted people
from accessing your SSH agent.
Discovery 2017-01-29 Entry 2017-03-16 putty
< 0.68
http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-agent-fwd-overflow.html
CVE-2017-6542
|