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.

393,392

Total vulnerabilities in the database

Vulnerabilities for products matching "openssl"

Found 8 matching products. Filters apply to all results.

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

openssl / openssl

295 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2009-2409	Medium	July 30, 2009 7/30/09	`>= 0.9.8, <= 0.9.8k`
CVE-2009-1386	Medium	June 4, 2009 6/4/09	`> 0.9.8, < 0.9.8i`
CVE-2009-1387	Medium	June 4, 2009 6/4/09	`>= 0.9.8, < 0.9.8m`
CVE-2009-1377	Medium	May 19, 2009 5/19/09	`>= 0.9.8, < 0.9.8m`
CVE-2009-1378	Medium	May 19, 2009 5/19/09	`> 0.9.8, < 0.9.8m`
CVE-2009-1379	Medium	May 19, 2009 5/19/09	`= 1.0.0-beta2`
CVE-2009-0789	Medium	March 27, 2009 3/27/09	`<= 0.9.8j` `= 0.9.1c` `= 0.9.2b` `= 0.9.3` `= 0.9.3a` `= 0.9.4` `= 0.9.5` `= 0.9.5-beta1` `= 0.9.5-beta2` `= 0.9.5a` `= 0.9.5a-beta1` `= 0.9.5a-beta2` `= 0.9.6` `= 0.9.6-beta1` `= 0.9.6-beta2` `= 0.9.6-beta3` `= 0.9.6a` `= 0.9.6a-beta1` `= 0.9.6a-beta2` `= 0.9.6a-beta3` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6f` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.6j` `= 0.9.6k` `= 0.9.6l` `= 0.9.6m` `= 0.9.7` `= 0.9.7-beta1` `= 0.9.7-beta2` `= 0.9.7-beta3` `= 0.9.7-beta4` `= 0.9.7-beta5` `= 0.9.7-beta6` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c` `= 0.9.7d` `= 0.9.7e` `= 0.9.7f` `= 0.9.7g` `= 0.9.7h` `= 0.9.7i` `= 0.9.7j` `= 0.9.7k` `= 0.9.7l` `= 0.9.7m` `= 0.9.8` `= 0.9.8a` `= 0.9.8b` `= 0.9.8c` `= 0.9.8d` `= 0.9.8e` `= 0.9.8f` `= 0.9.8g` `= 0.9.8h` `= 0.9.8i`
CVE-2009-0591	Low	March 27, 2009 3/27/09	`= 0.9.8h` `= 0.9.8i` `= 0.9.8j`
CVE-2009-0590	Medium	March 27, 2009 3/27/09	`< 0.9.8k`
CVE-2009-0653	High	February 20, 2009 2/20/09	`= 0.9.6`
CVE-2008-5077	Medium	January 7, 2009 1/7/09	`<= 0.9.8h` `= 0.9.1c` `= 0.9.2b` `= 0.9.3` `= 0.9.3a` `= 0.9.4` `= 0.9.5` `= 0.9.5-beta1` `= 0.9.5-beta2` `= 0.9.5a` `= 0.9.5a-beta1` `= 0.9.5a-beta2` `= 0.9.6` `= 0.9.6-beta1` `= 0.9.6-beta2` `= 0.9.6-beta3` `= 0.9.6a` `= 0.9.6a-beta1` `= 0.9.6a-beta2` `= 0.9.6a-beta3` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6f` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.6j` `= 0.9.6k` `= 0.9.6l` `= 0.9.6m` `= 0.9.7` `= 0.9.7-beta1` `= 0.9.7-beta2` `= 0.9.7-beta3` `= 0.9.7-beta4` `= 0.9.7-beta5` `= 0.9.7-beta6` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c` `= 0.9.7d` `= 0.9.7e` `= 0.9.7f` `= 0.9.7g` `= 0.9.7h` `= 0.9.7i` `= 0.9.7j` `= 0.9.7k` `= 0.9.7l` `= 0.9.8` `= 0.9.8a` `= 0.9.8b` `= 0.9.8c` `= 0.9.8d` `= 0.9.8e` `= 0.9.8f` `= 0.9.8g`
CVE-2008-1678	Medium	July 10, 2008 7/10/08	`= 0.9.8f` `= 0.9.8g` `= 0.9.8h`
CVE-2008-0891	Medium	May 29, 2008 5/29/08	`= 0.9.8f` `= 0.9.8g`
CVE-2008-1672	Medium	May 29, 2008 5/29/08	`= 0.9.8f` `= 0.9.8g`
CVE-2008-0166	High	May 13, 2008 5/13/08	`>= 0.9.8c-1, <= 0.9.8g`
CVE-2007-4995	High	October 13, 2007 10/13/07	`= 0.9.8` `= 0.9.8a` `= 0.9.8b` `= 0.9.8c` `= 0.9.8d` `= 0.9.8e`
CVE-2007-5135	Medium	September 27, 2007 9/27/07	`= 0.9.7` `= 0.9.7-beta1` `= 0.9.7-beta2` `= 0.9.7-beta3` `= 0.9.7-beta4` `= 0.9.7-beta5` `= 0.9.7-beta6` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c` `= 0.9.7d` `= 0.9.7e` `= 0.9.7f` `= 0.9.7g` `= 0.9.7h` `= 0.9.7i` `= 0.9.7j` `= 0.9.7k` `= 0.9.7l` `= 0.9.8` `= 0.9.8a` `= 0.9.8b` `= 0.9.8c` `= 0.9.8d` `= 0.9.8e` `= 0.9.8f`
CVE-2007-3108	Low	August 8, 2007 8/8/07	`<= 0.9.8e`
CVE-2006-2937	High	September 28, 2006 9/28/06	`= 0.9.7` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c` `= 0.9.7d` `= 0.9.7e` `= 0.9.7f` `= 0.9.7g` `= 0.9.7h` `= 0.9.7i` `= 0.9.7j` `= 0.9.7k` `= 0.9.8` `= 0.9.8a` `= 0.9.8b` `= 0.9.8c`
CVE-2006-2940	High	September 28, 2006 9/28/06	`= 0.9.1c` `= 0.9.2b` `= 0.9.3` `= 0.9.3a` `= 0.9.4` `= 0.9.5` `= 0.9.5-beta1` `= 0.9.5-beta2` `= 0.9.5a` `= 0.9.5a-beta1` `= 0.9.5a-beta2` `= 0.9.6` `= 0.9.6-beta1` `= 0.9.6-beta2` `= 0.9.6-beta3` `= 0.9.6a` `= 0.9.6a-beta1` `= 0.9.6a-beta2` `= 0.9.6a-beta3` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6f` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.6j` `= 0.9.6k` `= 0.9.6l` `= 0.9.6m` `= 0.9.7` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c` `= 0.9.7d` `= 0.9.7e` `= 0.9.7f` `= 0.9.7g` `= 0.9.7h` `= 0.9.7i` `= 0.9.7j` `= 0.9.7k` `= 0.9.8` `= 0.9.8a` `= 0.9.8b` `= 0.9.8c`
CVE-2006-3738	High	September 28, 2006 9/28/06	`= 0.9.7` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c` `= 0.9.7d` `= 0.9.7e` `= 0.9.7f` `= 0.9.7g` `= 0.9.7h` `= 0.9.7i` `= 0.9.7j` `= 0.9.7k` `= 0.9.8` `= 0.9.8a` `= 0.9.8b` `= 0.9.8c`
CVE-2006-4343	Medium	September 28, 2006 9/28/06	`= 0.9.7` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c` `= 0.9.7d` `= 0.9.7e` `= 0.9.7f` `= 0.9.7g` `= 0.9.7h` `= 0.9.7i` `= 0.9.7j` `= 0.9.7k` `= 0.9.8` `= 0.9.8a` `= 0.9.8b` `= 0.9.8c`
CVE-2006-4339	Medium	September 5, 2006 9/5/06	`<= 0.9.7` `= 0.9.1c` `= 0.9.2b` `= 0.9.3` `= 0.9.3a` `= 0.9.4` `= 0.9.5` `= 0.9.5-beta1` `= 0.9.5-beta2` `= 0.9.5a` `= 0.9.5a-beta1` `= 0.9.5a-beta2` `= 0.9.6` `= 0.9.6-beta1` `= 0.9.6-beta2` `= 0.9.6-beta3` `= 0.9.6a` `= 0.9.6a-beta1` `= 0.9.6a-beta2` `= 0.9.6a-beta3` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6f` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.6j` `= 0.9.6k` `= 0.9.6l` `= 0.9.6m` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c` `= 0.9.7d` `= 0.9.7e` `= 0.9.7f` `= 0.9.7g` `= 0.9.7h` `= 0.9.7i` `= 0.9.7j` `= 0.9.8` `= 0.9.8a` `= 0.9.8b`
CVE-2005-2969	Medium	October 18, 2005 10/18/05	`= 0.9.7` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c` `= 0.9.7d` `= 0.9.7e` `= 0.9.7f` `= 0.9.7g` `= 0.9.8`
CVE-2005-2946	High	September 16, 2005 9/16/05	`< 0.9.8`
CVE-2005-1797	Medium	May 26, 2005 5/26/05	`= 0.9.1c` `= 0.9.2b` `= 0.9.3` `= 0.9.4` `= 0.9.5` `= 0.9.5a` `= 0.9.6` `= 0.9.6a` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6f` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.6j` `= 0.9.6k` `= 0.9.6l` `= 0.9.6m` `= 0.9.7` `= 0.9.7-beta1` `= 0.9.7-beta2` `= 0.9.7-beta3` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c` `= 0.9.7d`
CVE-2004-0975	Low	February 9, 2005 2/9/05	`= 0.9.6` `= 0.9.6a` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6f` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.6j` `= 0.9.6k` `= 0.9.6l` `= 0.9.6m` `= 0.9.7c` `= 0.9.7d`
CVE-2004-0079	High	November 23, 2004 11/23/04	`= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6f` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.6j` `= 0.9.6k` `= 0.9.7` `= 0.9.7-beta1` `= 0.9.7-beta2` `= 0.9.7-beta3` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c`
CVE-2004-0081	Medium	November 23, 2004 11/23/04	`= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6f` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.6j` `= 0.9.6k` `= 0.9.7` `= 0.9.7-beta1` `= 0.9.7-beta2` `= 0.9.7-beta3` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c`
CVE-2004-0112	Medium	November 23, 2004 11/23/04	`= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6f` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.6j` `= 0.9.6k` `= 0.9.7` `= 0.9.7-beta1` `= 0.9.7-beta2` `= 0.9.7-beta3` `= 0.9.7a` `= 0.9.7b` `= 0.9.7c`
CVE-2003-0851	Medium	December 1, 2003 12/1/03	`= 0.9.6` `= 0.9.6a` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6f` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.6j` `= 0.9.6k` `= 0.9.7` `= 0.9.7a` `= 0.9.7b`
CVE-2002-1568	Medium	November 17, 2003 11/17/03	`= 0.9.6e`
CVE-2003-0543	Medium	November 17, 2003 11/17/03	`= 0.9.6` `= 0.9.7`
CVE-2003-0544	Medium	November 17, 2003 11/17/03	`= 0.9.6` `= 0.9.7`
CVE-2003-0545	Critical	November 17, 2003 11/17/03	`= 0.9.6` `= 0.9.7`
CVE-2003-0147	Medium	March 31, 2003 3/31/03	`= 0.9.6` `= 0.9.6a` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.7` `= 0.9.7a`
CVE-2003-0131	High	March 24, 2003 3/24/03	`= 0.9.6` `= 0.9.6a` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.6e` `= 0.9.6g` `= 0.9.6h` `= 0.9.6i` `= 0.9.7` `= 0.9.7a`
CVE-2003-0078	Medium	March 3, 2003 3/3/03	`< 0.9.6i` `= 0.9.6i` `= 0.9.7` `= 0.9.7-beta1` `= 0.9.7-beta2` `= 0.9.7-beta3` `= 0.9.7-beta4` `= 0.9.7-beta5` `= 0.9.7-beta6`
CVE-2002-0655	High	August 12, 2002 8/12/02	`= 0.9.1c` `= 0.9.2b` `= 0.9.3` `= 0.9.4` `= 0.9.5` `= 0.9.5a` `= 0.9.6` `= 0.9.6a` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.7-beta1` `= 0.9.7-beta2`
CVE-2002-0656	High	August 12, 2002 8/12/02	`= 0.9.1c` `= 0.9.2b` `= 0.9.3` `= 0.9.4` `= 0.9.5` `= 0.9.5a` `= 0.9.6` `= 0.9.6a` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.7-beta1` `= 0.9.7-beta2`
CVE-2002-0657	High	August 12, 2002 8/12/02	`= 0.9.7-beta1` `= 0.9.7-beta2`
CVE-2002-0659	Medium	August 12, 2002 8/12/02	`= 0.9.1c` `= 0.9.2b` `= 0.9.3` `= 0.9.4` `= 0.9.5` `= 0.9.5a` `= 0.9.6` `= 0.9.6a` `= 0.9.6b` `= 0.9.6c` `= 0.9.6d` `= 0.9.7-beta1` `= 0.9.7-beta2`
CVE-2001-1141	Medium	July 10, 2001 7/10/01	`= 0.9.1c` `= 0.9.2b` `= 0.9.3` `= 0.9.4` `= 0.9.5` `= 0.9.6` `= 0.9.6a`
CVE-2000-0535	Medium	June 12, 2000 6/12/00	`= 0.9.4`
CVE-1999-0428	High	March 22, 1999 3/22/99	`< 0.9.2b`

Showing vulnerabilities for 8 products matching "openssl". 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.