Overview 46 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 9 public PoC · 0 EPSS ≥ 0.5
46matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
9public PoC19.6%
0EPSS ≥ 0.50.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
46
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
46
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
9
19.6%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
37
80.4%
split by
peak 13 / year
19984
Not applicable4
High2
Medium2
not blocked4
No public exploit4
19995
Not applicable5
High2
Medium2
Low1
not blocked5
Working exploit published1
No public exploit4
20004
Not applicable4
High1
Medium3
not blocked4
Working exploit published1
No public exploit3
200113
Not applicable13
High7
Medium5
Low1
not blocked13
Working exploit published5
No public exploit8
20024
Not applicable4
High4
not blocked4
Working exploit published1
No public exploit3
20032
Not applicable2
Medium1
Low1
not blocked2
No public exploit2
20040
20052
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20063
Not applicable3
High2
Medium1
not blocked3
No public exploit3
20071
Not applicable1
Medium1
not blocked1
No public exploit1
20082
Not applicable2
High1
Low1
not blocked2
No public exploit2
20090
20100
20111
Not applicable1
High1
not blocked1
No public exploit1
20121
Not applicable1
High1
not blocked1
Working exploit published1
20130
20140
20150
20160
20170
20180
20190
20200
20213
Not applicable3
High3
not blocked3
No public exploit3
20220
20230
20241
Not applicable1
Critical1
not blocked1
No public exploit1
200020032006200920122015201820212024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-30170 | Critical | 2024-08-06 | Not applicable | No public exploit | PrivX before 34.0 allows data exfiltration and denial of service via the REST API. This is fixed in minor versions 33.1, 32.3, 31.3, and later, and in major version 34.0 and later, |
| CVE-2021-27893 | High | 2021-03-15 | Not applicable | No public exploit | SSH Tectia Client and Server before 6.4.19 on Windows allow local privilege escalation in nonstandard conditions. ConnectSecure on Windows is affected. |
| CVE-2021-27892 | High | 2021-03-15 | Not applicable | No public exploit | SSH Tectia Client and Server before 6.4.19 on Windows allow local privilege escalation. ConnectSecure on Windows is affected. |
| CVE-2021-27891 | High | 2021-03-15 | Not applicable | No public exploit | SSH Tectia Client and Server before 6.4.19 on Windows have weak key generation. ConnectSecure on Windows is affected. |
| CVE-2012-5975 | High | 2012-12-04 | Not applicable | Working exploit published | The SSH USERAUTH CHANGE REQUEST feature in SSH Tectia Server 6.0.4 through 6.0.20, 6.1.0 through 6.1.12, 6.2.0 through 6.2.5, and 6.3.0 through 6.3.2 on UNIX and Linux, when old-style password authentication is enabled, allows remote attackers to bypass authentication via a crafted session involving entry of blank passwords, as demonstrated by a root login session from a modified OpenSSH client with an added input_userauth_passwd_changereq call in sshconnect2.c. |
| CVE-2011-0766 | High | 2011-05-31 | Not applicable | No public exploit | The random number generator in the Crypto application before 2.0.2.2, and SSH before 2.0.5, as used in the Erlang/OTP ssh library before R14B03, uses predictable seeds based on the current time, which makes it easier for remote attackers to guess DSA host and SSH session keys. |
| CVE-2008-5161 | Low | 2008-11-19 | Not applicable | No public exploit | Error handling in the SSH protocol in (1) SSH Tectia Client and Server and Connector 4.0 through 4.4.11, 5.0 through 5.2.4, and 5.3 through 5.3.8; Client and Server and ConnectSecure 6.0 through 6.0.4; Server for Linux on IBM System z 6.0.4; Server for IBM z/OS 5.5.1 and earlier, 6.0.0, and 6.0.1; and Client 4.0-J through 4.3.3-J and 4.0-K through 4.3.10-K; and (2) OpenSSH 4.7p1 and possibly other versions, when using a block cipher algorithm in Cipher Block Chaining (CBC) mode, makes it easier for remote attackers to recover certain plaintext data from an arbitrary block of ciphertext in an SSH session via unknown vectors. |
| CVE-2007-5616 | High | 2008-01-09 | Not applicable | No public exploit | ssh-signer in SSH Tectia Client and Server 5.x before 5.2.4, and 5.3.x before 5.3.6, on Unix and Linux allows local users to gain privileges via unspecified vectors. |
| CVE-2007-2063 | Medium | 2007-04-18 | Not applicable | No public exploit | SSH Tectia Server for IBM z/OS before 5.4.0 uses insecure world-writable permissions for (1) the server pid file, which allows local users to cause arbitrary processes to be stopped, or (2) when _BPX_BATCH_UMASK is missing from the environment, creates HFS files with insecure permissions, which allows local users to read or modify these files and have other unknown impact. |
| CVE-2006-5484 | Medium | 2006-10-24 | Not applicable | No public exploit | SSH Tectia Client/Server/Connector 5.1.0 and earlier, Manager 2.2.0 and earlier, and other products, when using an RSA key with exponent 3, removes PKCS-1 padding before generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents Tectia from correctly verifying X.509 and other certificates that use PKCS #1, a similar issue to CVE-2006-4339. |
| CVE-2006-4316 | High | 2006-08-23 | Not applicable | No public exploit | SSH Tectia Management Agent 2.1.2 allows local users to gain root privileges by running a program called sshd, which is obtained from a process listing when the "Restart" action is selected from the Management server GUI, which causes the agent to locate the pathname of the user's program and restart it with root privileges. |
| CVE-2006-4315 | High | 2006-08-23 | Not applicable | No public exploit | Unquoted Windows search path vulnerability in multiple SSH Tectia products, including Client/Server/Connector 5.0.0 and 5.0.1 and Client/Server before 4.4.5, and Manager 2.12 and earlier, when running on Windows, might allow local users to gain privileges via a malicious program file under "Program Files" or its subdirectories. |
| CVE-2005-4310 | High | 2005-12-17 | Not applicable | No public exploit | SSH Tectia Server 5.0.0 (A, F, and T), when allowing host-based authentication only, allows users to log in with the wrong credentials. |
| CVE-2005-2146 | Medium | 2005-07-05 | Not applicable | No public exploit | SSH Tectia Server 4.3.1 and earlier, and SSH Secure Shell for Windows Servers, uses insecure permissions when generating the Secure Shell host identification key, which allows local users to access the key and spoof the server. |
| CVE-2003-1120 | Low | 2003-12-31 | Not applicable | No public exploit | Race condition in SSH Tectia Server 4.0.3 and 4.0.4 for Unix, when the password change plugin (ssh-passwd-plugin) is enabled, allows local users to obtain the server's private key. |
| CVE-2003-1119 | Medium | 2003-12-31 | Not applicable | No public exploit | SSH Secure Shell before 3.2.9 allows remote attackers to cause a denial of service via malformed BER/DER packets. |
| CVE-2002-1715 | High | 2002-12-31 | Not applicable | Working exploit published | SSH 1 through 3, and possibly other versions, allows local users to bypass restricted shells such as rbash or rksh by uploading a script to a world-writeable directory, then executing that script to gain normal shell access. |
| CVE-2002-1646 | High | 2002-12-31 | Not applicable | No public exploit | SSH Secure Shell for Servers 3.0.0 to 3.1.1 allows remote attackers to override the AllowedAuthentications configuration and use less secure authentication schemes (e.g. password) than configured for the server. |
| CVE-2002-1645 | High | 2002-11-25 | Not applicable | No public exploit | Buffer overflow in the URL catcher feature for SSH Secure Shell for Workstations client 3.1 to 3.2.0 allows remote attackers to execute arbitrary code via a long URL. |
| CVE-2002-1644 | High | 2002-11-25 | Not applicable | No public exploit | SSH Secure Shell for Servers and SSH Secure Shell for Workstations 2.0.13 through 3.2.1, when running without a PTY, does not call setsid to remove the child process from the process group of the parent process, which allows attackers to gain certain privileges. |
| CVE-2001-0572 | High | 2001-08-22 | Not applicable | No public exploit | The SSH protocols 1 and 2 (aka SSH-2) as implemented in OpenSSH and other packages have various weaknesses which can allow a remote attacker to obtain the following information via sniffing: (1) password lengths or ranges of lengths, which simplifies brute force password guessing, (2) whether RSA or DSA authentication is being used, (3) the number of authorized_keys in RSA authentication, or (4) the lengths of shell commands. |
| CVE-2001-0553 | High | 2001-08-14 | Not applicable | Working exploit published | SSH Secure Shell 3.0.0 on Unix systems does not properly perform password authentication to the sshd2 daemon, which allows local users to gain access to accounts with short password fields, such as locked accounts that use "NP" in the password field. |
| CVE-2001-0471 | High | 2001-06-27 | Not applicable | Working exploit published | SSH daemon version 1 (aka SSHD-1 or SSH-1) 1.2.30 and earlier does not log repeated login attempts, which could allow remote attackers to compromise accounts without detection via a brute force attack. |
| CVE-2001-0364 | Medium | 2001-06-27 | Not applicable | No public exploit | SSH Communications Security sshd 2.4 for Windows allows remote attackers to create a denial of service via a large number of simultaneous connections. |
| CVE-2001-0361 | Medium | 2001-06-27 | Not applicable | No public exploit | Implementations of SSH version 1.5, including (1) OpenSSH up to version 2.3.0, (2) AppGate, and (3) ssh-1 up to version 1.2.31, in certain configurations, allow a remote attacker to decrypt and/or alter traffic via a "Bleichenbacher attack" on PKCS#1 version 1.5. |
| CVE-2001-0259 | Low | 2001-06-02 | Not applicable | Working exploit published | ssh-keygen in ssh 1.2.27 - 1.2.30 with Secure-RPC can allow local attackers to recover a SUN-DES-1 magic phrase generated by another user, which the attacker can use to decrypt that user's private key file. |
| CVE-2001-0144 | High | 2001-03-12 | Not applicable | Working exploit published | CORE SDI SSH1 CRC-32 compensation attack detector allows remote attackers to execute arbitrary commands on an SSH server or client via an integer overflow. |
| CVE-2001-1476 | High | 2001-01-18 | Not applicable | No public exploit | SSH before 2.0, with RC4 encryption and the "disallow NULL passwords" option enabled, makes it easier for remote attackers to guess portions of user passwords by replaying user sessions with certain modifications, which trigger different messages depending on whether the guess is correct or not. |
| CVE-2001-1475 | High | 2001-01-18 | Not applicable | No public exploit | SSH before 2.0, when using RC4 and password authentication, allows remote attackers to replay messages until a new server key (VK) is generated. |
| CVE-2001-1474 | Medium | 2001-01-18 | Not applicable | No public exploit | SSH before 2.0 disables host key checking when connecting to the localhost, which allows remote attackers to silently redirect connections to the localhost by poisoning the client's DNS cache. |
| CVE-2001-1473 | High | 2001-01-18 | Not applicable | Working exploit published | The SSH-1 protocol allows remote servers to conduct man-in-the-middle attacks and replay a client challenge response to a target server by creating a Session ID that matches the Session ID of the target, but which uses a public key pair that is weaker than the target's public key, which allows the attacker to compute the corresponding private key and use the target's Session ID with the compromised key pair to masquerade as the target. |
| CVE-2001-1470 | Medium | 2001-01-18 | Not applicable | No public exploit | The IDEA cipher as implemented by SSH1 does not protect the final block of a message against modification, which allows remote attackers to modify the block without detection by changing its cyclic redundancy check (CRC) to match the modifications to the message. |
| CVE-2001-1469 | Medium | 2001-01-18 | Not applicable | No public exploit | The RC4 stream cipher as used by SSH1 allows remote attackers to modify messages without detection by XORing the original message's cyclic redundancy check (CRC) with the CRC of a mask consisting of all the bits of the original message that were modified. |
| CVE-2000-0992 | Medium | 2000-12-19 | Not applicable | Working exploit published | Directory traversal vulnerability in scp in sshd 1.2.xx allows a remote malicious scp server to overwrite arbitrary files via a .. (dot dot) attack. |
| CVE-2000-0575 | High | 2000-07-05 | Not applicable | No public exploit | SSH 1.2.27 with Kerberos authentication support stores Kerberos tickets in a file which is created in the current directory of the user who is logging in, which could allow remote attackers to sniff the ticket cache if the home directory is installed on NFS. |
| CVE-2000-0217 | Medium | 2000-02-24 | Not applicable | No public exploit | The default configuration of SSH allows X forwarding, which could allow a remote attacker to control a client's X sessions via a malicious xauth program. |
| CVE-2000-0143 | Medium | 2000-02-11 | Not applicable | No public exploit | The SSH protocol server sshd allows local users without shell access to redirect a TCP connection through a service that uses the standard system password database for authentication, such as POP or FTP. |
| CVE-1999-0787 | Low | 1999-09-17 | Not applicable | Working exploit published | The SSH authentication agent follows symlinks via a UNIX domain socket. |
| CVE-1999-1231 | Medium | 1999-06-09 | Not applicable | No public exploit | ssh 2.0.12, and possibly other versions, allows valid user names to attempt to enter the correct password multiple times, but only prompts an invalid user name for a password once, which allows remote attackers to determine user account names on the server. |
| CVE-1999-1029 | High | 1999-05-13 | Not applicable | No public exploit | SSH server (sshd2) before 2.0.12 does not properly record login attempts if the connection is closed before the maximum number of tries, allowing a remote attacker to guess the password without showing up in the audit logs. |
| CVE-1999-0398 | Medium | 1999-01-01 | Not applicable | No public exploit | In some instances of SSH 1.2.27 and 2.0.11 on Linux systems, SSH will allow users with expired accounts to login. |
| CVE-1999-0248 | High | 1999-01-01 | Not applicable | No public exploit | A race condition in the authentication agent mechanism of sshd 1.2.17 allows an attacker to steal another user's credentials. |
| CVE-1999-1159 | Medium | 1998-12-29 | Not applicable | No public exploit | SSH 2.0.11 and earlier allows local users to request remote forwarding from privileged ports without being root. |
| CVE-1999-0310 | High | 1998-09-01 | Not applicable | No public exploit | SSH 1.2.25 on HP-UX allows access to new user accounts. |
| CVE-1999-1085 | Medium | 1998-06-12 | Not applicable | No public exploit | SSH 1.2.25, 1.2.23, and other versions, when used in in CBC (Cipher Block Chaining) or CFB (Cipher Feedback 64 bits) modes, allows remote attackers to insert arbitrary data into an existing stream between an SSH client and server by using a known plaintext attack and computing a valid CRC-32 checksum for the packet, aka the "SSH insertion attack." |
| CVE-1999-0013 | High | 1998-01-22 | Not applicable | No public exploit | Stolen credentials from SSH clients via ssh-agent program, allowing other local users to access remote accounts belonging to the ssh-agent user. |