| 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/
|
| 080936ba-fbb7-11ee-abc8-6960f2492b1d | PuTTY and embedders (f.i., filezilla) -- biased RNG with NIST P521/ecdsa-sha2-nistp521 signatures permits recovering private key
Simon Tatham reports:
ECDSA signatures using 521-bit keys (the NIST P521 curve,
otherwise known as ecdsa-sha2-nistp521) were generated with biased
random numbers. This permits an attacker in possession of a few
dozen signatures to RECOVER THE PRIVATE KEY.
Any 521-bit ECDSA private key that PuTTY or Pageant has used to
sign anything should be considered compromised.
Additionally, if you have any 521-bit ECDSA private keys that
you've used with PuTTY, you should consider them to be
compromised: generate new keys, and remove the old public keys
from any authorized_keys files.
A second, independent scenario is that the adversary is an operator
of an SSH server to which the victim authenticates (for remote login
or file copy), [...] and the victim uses the same private key for
SSH connections to other services operated by other entities. Here,
the rogue server operator (who would otherwise have no way to
determine the victim's private key) can derive the victim's private
key, and then use it for unauthorized access to those other
services. If the other services include Git services, then again it
may be possible to conduct supply-chain attacks on software
maintained in Git. This also affects, for example, FileZilla before
3.67.0, WinSCP before 6.3.3, TortoiseGit before 2.15.0.1, and
TortoiseSVN through 1.14.6.
Discovery 2024-04-01
Entry 2024-04-16
putty
>= 0.68 lt 0.81
putty-nogtk
>= 0.68 lt 0.81
filezilla
< 3.67.0
CVE-2024-31497
https://lists.tartarus.org/pipermail/putty-announce/2024/000038.html
https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-p521-bias.html
https://git.tartarus.org/?h=c193fe9848f50a88a4089aac647fecc31ae96d27&p=simon/putty.git
https://filezilla-project.org/versions.php
https://nvd.nist.gov/vuln/detail/CVE-2024-31497
|