VuXML ID | Description |
91955195-9ebb-11ee-bc14-a703705db3a6 | putty -- add protocol extension against 'Terrapin attack'
Simon Tatham reports:
PuTTY version 0.80 [contains] one security fix [...] for a newly discovered security issue known as the 'Terrapin'
attack, also numbered CVE-2023-48795. The issue affects widely-used
OpenSSH extensions to the SSH protocol: the ChaCha20+Poly1305
cipher system, and 'encrypt-then-MAC' mode.
In order to benefit from the fix, you must be using a fixed version
of PuTTY _and_ a server with the fix, so that they can agree to
adopt a modified version of the protocol. [...]
Discovery 2023-10-16 Entry 2023-12-19 putty
< 0.80
putty-nogtk
< 0.80
CVE-2023-48795
https://lists.tartarus.org/pipermail/putty-announce/2023/000037.html
https://www.openssh.com/txt/release-9.6
https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html
https://terrapin-attack.com/
|
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
|
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
|