Overview 33 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 7 public PoC · 1 EPSS ≥ 0.5
33matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
7public PoC21.2%
1EPSS ≥ 0.53.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
33
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
33
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
5
15.2%
Proof of concept only
3
9.1%
Forecast only
0
0.0%
No public exploit
25
75.8%
split by
peak 5 / year
20001
Not applicable1
Medium1
not blocked1
Working exploit published1
20010
20024
Not applicable4
High4
not blocked4
Working exploit published1
No public exploit3
20032
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20041
Not applicable1
High1
not blocked1
No public exploit1
20052
Not applicable2
High2
not blocked2
No public exploit2
20060
20071
Not applicable1
Low1
not blocked1
No public exploit1
20080
20090
20100
20110
20120
20135
Not applicable5
Medium3
Low2
not blocked5
No public exploit5
20140
20152
Not applicable2
Medium1
Low1
not blocked2
No public exploit2
20161
Not applicable1
Critical1
not blocked1
Working exploit published1
20173
Not applicable3
Critical1
High2
not blocked3
Working exploit published2
No public exploit1
20180
20194
Not applicable4
Critical2
High2
not blocked4
Proof of concept only1
No public exploit3
20200
20212
Not applicable2
High2
not blocked2
No public exploit2
20220
20230
20241
Not applicable1
Medium1
not blocked1
Proof of concept only1
20250
20264
Not applicable4
Medium1
Low3
not blocked4
Proof of concept only1
No public exploit3
200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-48852 | Low | 2026-05-25 | Not applicable | No public exploit | PuTTY 0.71 before 0.84 has an assertion failure in ECDSA signature verification. |
| CVE-2026-48851 | Low | 2026-05-25 | Not applicable | No public exploit | PuTTY 0.77 before 0.84 uses a copy of the PuTTY icon as a trust indication for TELNET data but the trust status is not cleared between proxy authentication and the main session. |
| CVE-2026-48850 | Medium | 2026-05-25 | Not applicable | No public exploit | PuTTY 0.72 before 0.84 has a double free in RSA KEX. |
| CVE-2026-4115 | Low | 2026-03-22 | Not applicable | Proof of concept only | A vulnerability was detected in PuTTY 0.83. Affected is the function eddsa_verify of the file crypto/ecc-ssh.c of the component Ed25519 Signature Handler. The manipulation results in improper verification of cryptographic signature. The attack may be performed from remote. The attack requires a high level of complexity. The exploitability is told to be difficult. The exploit is now public and may be used. The real existence of this vulnerability is still doubted at the moment. The patch is identified as af996b5ec27ab79bae3882071b9d6acf16044549. It is advisable to implement a patch to correct this issue. The vendor was contacted early, responded in a very professional manner and quickly released a patch for the affected product. However, at the moment there is no proof that this flaw might have any real-world impact. |
| CVE-2024-31497 | Medium | 2024-04-15 | Not applicable | Proof of concept only | In PuTTY 0.68 through 0.80 before 0.81, biased ECDSA nonce generation allows an attacker to recover a user's NIST P-521 secret key via a quick attack in approximately 60 signatures. This is especially important in a scenario where an adversary is able to read messages signed by PuTTY or Pageant. The required set of signed messages may be publicly readable because they are stored in a public Git service that supports use of SSH for commit signing, and the signatures were made by Pageant through an agent-forwarding mechanism. In other words, an adversary may already have enough signature information to compromise a victim's private key, even if there is no further use of vulnerable PuTTY versions. After a key compromise, an adversary may be able to conduct supply-chain attacks on software maintained in Git. 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), even though this server is not fully trusted by the victim, 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. |
| CVE-2021-36367 | High | 2021-07-09 | Not applicable | No public exploit | 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). |
| CVE-2021-33500 | High | 2021-05-21 | Not applicable | No public exploit | PuTTY before 0.75 on Windows allows remote servers to cause a denial of service (Windows GUI hang) by telling the PuTTY window to change its title repeatedly at high speed, which results in many SetWindowTextA or SetWindowTextW calls. NOTE: the same attack methodology may affect some OS-level GUIs on Linux or other platforms for similar reasons. |
| CVE-2019-17068 | High | 2019-10-01 | Not applicable | No public exploit | PuTTY before 0.73 mishandles the "bracketed paste mode" protection mechanism, which may allow a session to be affected by malicious clipboard content. |
| CVE-2019-17067 | Critical | 2019-10-01 | Not applicable | No public exploit | PuTTY before 0.73 on Windows improperly opens port-forwarding listening sockets, which allows attackers to listen on the same port to steal an incoming connection. |
| CVE-2019-9896 | High | 2019-03-21 | Not applicable | Proof of concept only | In PuTTY versions before 0.71 on Windows, local attackers could hijack the application by putting a malicious help file in the same directory as the executable. |
| CVE-2019-9895 | Critical | 2019-03-21 | Not applicable | No public exploit | In PuTTY versions before 0.71 on Unix, a remotely triggerable buffer overflow exists in any kind of server-to-client forwarding. |
| CVE-2017-7183 | High | 2017-03-27 | Not applicable | Working exploit published | The TFTP server in ExtraPuTTY 0.30 and earlier allows remote attackers to cause a denial of service (crash) via a large (1) read or (2) write TFTP protocol message. |
| CVE-2017-6542 | Critical | 2017-03-27 | Not applicable | Working exploit published | The ssh_agent_channel_data function in PuTTY before 0.68 allows remote attackers to have unspecified impact via a large length value in an agent protocol message and leveraging the ability to connect to the Unix-domain socket representing the forwarded agent connection, which trigger a buffer overflow. |
| CVE-2016-6167 | High | 2017-01-30 | Not applicable | No public exploit | Multiple untrusted search path vulnerabilities in Putty beta 0.67 allow local users to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse (1) UxTheme.dll or (2) ntmarta.dll file in the current working directory. |
| CVE-2016-2563 | Critical | 2016-04-07 | Not applicable | Working exploit published | Stack-based buffer overflow in the SCP command-line utility in PuTTY before 0.67 and KiTTY 0.66.6.3 and earlier allows remote servers to cause a denial of service (stack memory corruption) or execute arbitrary code via a crafted SCP-SINK file-size response to an SCP download request. |
| CVE-2015-5309 | Medium | 2015-12-07 | Not applicable | No public exploit | Integer overflow in the terminal emulator in PuTTY before 0.66 allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via an ECH (erase characters) escape sequence with a large parameter value, which triggers a buffer underflow. |
| CVE-2015-2157 | Low | 2015-03-27 | Not applicable | No public exploit | The (1) ssh2_load_userkey and (2) ssh2_save_userkey functions in PuTTY 0.51 through 0.63 do not properly wipe SSH-2 private keys from memory, which allows local users to obtain sensitive information by reading the memory. |
| CVE-2011-4607 | Low | 2013-08-23 | Not applicable | No public exploit | PuTTY 0.59 through 0.61 does not clear sensitive process memory when managing user replies that occur during keyboard-interactive authentication, which might allow local users to read login passwords by obtaining access to the process' memory. |
| CVE-2013-4852 | Medium | 2013-08-19 | Not applicable | No public exploit | Integer overflow in PuTTY 0.62 and earlier, WinSCP before 5.1.6, and other products that use PuTTY allows remote SSH servers to cause a denial of service (crash) and possibly execute arbitrary code in certain applications that use PuTTY via a negative size value in an RSA key signature during the SSH handshake, which triggers a heap-based buffer overflow. |
| CVE-2013-4208 | Low | 2013-08-19 | Not applicable | No public exploit | The rsa_verify function in PuTTY before 0.63 (1) does not clear sensitive process memory after use and (2) does not free certain structures containing sensitive process memory, which might allow local users to discover private RSA and DSA keys. |
| CVE-2013-4207 | Medium | 2013-08-19 | Not applicable | No public exploit | Buffer overflow in sshbn.c in PuTTY before 0.63 allows remote SSH servers to cause a denial of service (crash) via an invalid DSA signature that is not properly handled during computation of a modular inverse and triggers the overflow during a division by zero by the bignum functionality, a different vulnerability than CVE-2013-4206. |
| CVE-2013-4206 | Medium | 2013-08-19 | Not applicable | No public exploit | Heap-based buffer underflow in the modmul function in sshbn.c in PuTTY before 0.63 allows remote SSH servers to cause a denial of service (crash) and possibly trigger memory corruption or code execution via a crafted DSA signature, which is not properly handled when performing certain bit-shifting operations during modular multiplication. |
| CVE-2006-7162 | Low | 2007-03-07 | Not applicable | No public exploit | PuTTY 0.59 and earlier uses weak file permissions for (1) ppk files containing private keys generated by puttygen and (2) session logs created by putty, which allows local users to gain sensitive information by reading these files. |
| CVE-2005-0467 | High | 2005-02-21 | Not applicable | No public exploit | Multiple integer overflows in the (1) sftp_pkt_getstring and (2) fxp_readdir_recv functions in the PSFTP and PSCP clients for PuTTY 0.56, and possibly earlier versions, allow remote malicious web sites to execute arbitrary code via SFTP responses that corrupt the heap after insufficient memory has been allocated. |
| CVE-2004-1008 | High | 2005-01-10 | Not applicable | No public exploit | Integer signedness error in the ssh2_rdpkt function in PuTTY before 0.56 allows remote attackers to execute arbitrary code via a SSH2_MSG_DEBUG packet with a modified stringlen parameter, which leads to a buffer overflow. |
| CVE-2004-1440 | High | 2004-12-31 | Not applicable | No public exploit | Multiple heap-based buffer overflows in the modpow function in PuTTY before 0.55 allow (1) remote attackers to execute arbitrary code via an SSH2 packet with a base argument that is larger than the mod argument, which causes the modpow function to write memory before the beginning of its buffer, and (2) remote malicious servers to cause a denial of service (client crash) and possibly execute arbitrary code via a large bignum during authentication. |
| CVE-2003-0069 | High | 2003-03-18 | Not applicable | No public exploit | The PuTTY terminal emulator 0.53 allows attackers to modify the window title via a certain character escape sequence and then insert it back to the command line in the user's terminal, e.g. when the user views a file containing the malicious sequence, which could allow the attacker to execute arbitrary commands. |
| CVE-2003-0048 | Medium | 2003-02-19 | Not applicable | No public exploit | PuTTY 0.53b and earlier does not clear logon credentials from memory, including plaintext passwords, which could allow attackers with access to memory to steal the SSH credentials. |
| CVE-2002-1360 | High | 2002-12-23 | Not applicable | No public exploit | Multiple SSH2 servers and clients do not properly handle strings with null characters in them when the string length is specified by a length field, which could allow remote attackers to cause a denial of service or possibly execute arbitrary code due to interactions with the use of null-terminated strings as implemented using languages such as C, as demonstrated by the SSHredder SSH protocol test suite. |
| CVE-2002-1359 | High | 2002-12-23 | Not applicable | Working exploit published | Multiple SSH2 servers and clients do not properly handle large packets or large fields, which may allow remote attackers to cause a denial of service or possibly execute arbitrary code via buffer overflow attacks, as demonstrated by the SSHredder SSH protocol test suite. |
| CVE-2002-1358 | High | 2002-12-23 | Not applicable | No public exploit | Multiple SSH2 servers and clients do not properly handle lists with empty elements or strings, which may allow remote attackers to cause a denial of service or possibly execute arbitrary code, as demonstrated by the SSHredder SSH protocol test suite. |
| CVE-2002-1357 | High | 2002-12-23 | Not applicable | No public exploit | Multiple SSH2 servers and clients do not properly handle packets or data elements with incorrect length specifiers, which may allow remote attackers to cause a denial of service or possibly execute arbitrary code, as demonstrated by the SSHredder SSH protocol test suite. |
| CVE-2000-0476 | Medium | 2000-06-01 | Not applicable | Working exploit published | xterm, Eterm, and rxvt allow an attacker to cause a denial of service by embedding certain escape characters which force the window to be resized. |