How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

326,214

Total vulnerabilities in the database

Vulnerabilities for products matching "ssh"

Found 6 matching products. Filters apply to all results.

You can search for specific versions with /product/ssh/1.2.3

ssh / ssh

23 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2023-48795	Medium	December 18, 2023 12/18/23	< 4.9.1.5 >= 4.10 < 4.11.1.7 >= 4.12 < 4.13.2.4 >= 4.14 < 4.15.3.1 >= 5.0 < 5.1.1
CVE-2011-0766	High	May 31, 2011 5/31/11	<= 2.0.4
CVE-2002-1715	High	December 31, 2002 12/31/02	== 1.2.6 == 1.2.0 == 1.2.9 == 1.2.21 == 1.2.15 == 1.2.4 == 1.2.14 == 1.2.19 == 1.2.8 == 1.2.31 == 1.2.24 == 1.2.18 == 1.2.7 == 1.2.20 == 1.2.3 == 1.2.12 == 1.2.25 == 1.2.17 == 1.2.30 == 1.2.1 == 1.2.26 == 1.2.27 == 1.2.16 == 1.2.28 == 1.2.29 == 1.2.11 == 1.2.5 == 1.2.13 == 1.2.22 == 1.2.2 == 1.2.23 == 1.2.10
CVE-2001-0572	High	August 22, 2001 8/22/01	== 1.2.31 == 1.2.24 == 1.2.25 == 1.2.30 == 1.2.26 == 1.2.27 == 1.2.28 == 1.2.29
CVE-2001-0361	Low	June 27, 2001 6/27/01	<= 1.2.31
CVE-2001-0471	High	June 27, 2001 6/27/01	<= 1.2.30
CVE-2001-0259	Low	June 2, 2001 6/2/01	== 1.2.30 == 1.2.27 == 1.2.28 == 1.2.29
CVE-2001-0144	High	March 12, 2001 3/12/01	== 1.2.31 == 1.2.24 == 1.2.25 == 1.2.30 == 1.2.26 == 1.2.27 == 1.2.28 == 1.2.29
CVE-2001-1469	Medium	January 18, 2001 1/18/01	== 1.2.31 == 1.2.24 == 1.2.25 == 1.2.30 == 1.2.26 == 1.2.27 == 1.2.28 == 1.2.29
CVE-2001-1470	Medium	January 18, 2001 1/18/01	== 1.2.31 == 1.2.24 == 1.2.25 == 1.2.30 == 1.2.26 == 1.2.27 == 1.2.28 == 1.2.29
CVE-2001-1473	High	January 18, 2001 1/18/01	== 1.2.31 == 1.2.24 == 1.2.25 == 1.2.30 == 1.2.26 == 1.2.27 == 1.2.28 == 1.2.29
CVE-2001-1474	Medium	January 18, 2001 1/18/01	== 1.2.31 == 1.2.24 == 1.2.25 == 1.2.30 == 1.2.26 == 1.2.27 == 1.2.28 == 1.2.29
CVE-2001-1475	High	January 18, 2001 1/18/01	== 1.2.31 == 1.2.24 == 1.2.25 == 1.2.30 == 1.2.26 == 1.2.27 == 1.2.28 == 1.2.29
CVE-2001-1476	High	January 18, 2001 1/18/01	== 1.2.31 == 1.2.24 == 1.2.25 == 1.2.30 == 1.2.26 == 1.2.27 == 1.2.28 == 1.2.29
CVE-2000-0992	Medium	December 19, 2000 12/19/00	== 1.2.21 == 1.2.15 == 1.2.14 == 1.2.19 == 1.2.31 == 1.2.24 == 1.2.18 == 1.2.20 == 1.2.25 == 1.2.17 == 1.2.30 == 1.2.26 == 1.2.27 == 1.2.16 == 1.2.28 == 1.2.29 == 1.2.22 == 1.2.23
CVE-2000-0575	High	July 5, 2000 7/5/00	== 1.2.27
CVE-2000-0217	Medium	February 24, 2000 2/24/00	== 1.2.6 == 1.2.0 == 1.2.9 == 1.2.21 == 1.2.15 == 1.2.4 == 1.2.14 == 1.2.19 == 1.2.8 == 1.2.31 == 1.2.24 == 1.2.18 == 1.2.7 == 1.2.20 == 1.2.3 == 1.2.12 == 1.2.25 == 1.2.17 == 1.2.30 == 1.2.1 == 1.2.26 == 1.2.27 == 1.2.16 == 1.2.28 == 1.2.29 == 1.2.11 == 1.2.5 == 1.2.13 == 1.2.22 == 1.2.2 == 1.2.23 == 1.2.10
CVE-2000-0143	Low	February 11, 2000 2/11/00	== 1.2.6 == 1.2.0 == 1.2.9 == 1.2.21 == 1.2.15 == 1.2.4 == 1.2.14 == 1.2.19 == 1.2.8 == 1.2.24 == 1.2.18 == 1.2.7 == 1.2.20 == 1.2.3 == 1.2.12 == 1.2.25 == 1.2.17 == 1.2.1 == 1.2.26 == 1.2.27 == 1.2.16 == 1.2.11 == 1.2.5 == 1.2.13 == 1.2.22 == 1.2.2 == 1.2.23 == 1.2.10
CVE-1999-0787	Low	September 17, 1999 9/17/99	== 1.2.27
CVE-1999-0248	High	January 1, 1999 1/1/99	== 1.2.27
CVE-1999-0398	Low	January 1, 1999 1/1/99	== 1.2.27
CVE-1999-0310	High	September 1, 1998 9/1/98	== 1.2.25
CVE-1999-0013	High	January 22, 1998 1/22/98	== 1.2.6 == 1.2.0 == 1.2.9 == 1.2.4 == 1.2.14 == 1.2.8 == 1.2.7 == 1.2.3 == 1.2.12 == 1.2.1 == 1.2.11 == 1.2.5 == 1.2.13 == 1.2.2 == 1.2.10

jenkins / ssh

4 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-30958	High	May 17, 2022 5/17/22	<= 2.6.1
CVE-2022-30959	Medium	May 17, 2022 5/17/22	<= 2.6.1
CVE-2022-30957	Low	May 17, 2022 5/17/22	<= 2.6.1
CVE-2017-1000245	Medium	November 1, 2017 11/1/17	<= 2.4

golang / ssh

3 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2021-43565	High	September 6, 2022 9/6/22	< 0.0.0-20211202192323-5770296d904e
CVE-2022-27191	High	March 18, 2022 3/18/22	< 0.0.0-20220314234659-1baeb1ce4c0b
CVE-2020-29652	High	December 17, 2020 12/17/20	<= 0.0.0-20201203163018-be400aefbc4c

org.jenkins-ci.plugins / ssh

4 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-30959	Medium	May 17, 2022 5/17/22	<= 2.6.1
CVE-2022-30958	High	May 17, 2022 5/17/22	<= 2.6.1
CVE-2022-30957	Low	May 17, 2022 5/17/22	<= 2.6.1
CVE-2017-1000245	Medium	November 1, 2017 11/1/17	< 2.5

org.jvnet.hudson.plugins / ssh

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2017-1000245	Medium		November 1, 2017 11/1/17	<= 2.3

go / ssh

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2025-47913	High		November 13, 2025 11/13/25	< 0.43.0
CVE-2025-22869	High		February 26, 2025 2/26/25	< 0.35.0

Showing vulnerabilities for 6 products matching "ssh". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.