Ssh2 vulnerabilitiesRanked by how likely they are to be used.
Ssh2 is made by SSH. We track 9 published vulnerabilities in it, across 28 versions. None of them is on the list of flaws known to be exploited today. If you run Ssh2, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Ssh2 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Ssh2's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Ssh2 flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 7.9%CVE-2002-1645Critical
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.
- 1.6%CVE-2001-0364Medium
SSH Communications Security sshd 2.4 for Windows allows remote attackers to create a denial of service via a large number of simultaneous connections.
- 1.6%CVE-1999-1029High
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...
- 1.5%CVE-1999-1231Medium
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...
- 1.0%CVE-2000-0217Medium
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.
- 0.9%CVE-2002-1715High
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...
- 0.4%CVE-2002-1644High
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,...
- 0.4%CVE-1999-0398Medium
In some instances of SSH 1.2.27 and 2.0.11 on Linux systems, SSH will allow users with expired accounts to login.
- 0.3%CVE-1999-1159Medium
SSH 2.0.11 and earlier allows local users to request remote forwarding from privileged ports without being root.
Running Ssh2? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Ssh2 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 9 published vulnerabilities listed under the name Ssh2, across 28 versions.
None of Ssh2's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Ssh2. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.