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,895

Total vulnerabilities in the database

Vulnerabilities for products matching "strongswan"

Found 2 matching products. Filters apply to all results.

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

strongswan / strongswan

37 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-4967	High	May 14, 2024 5/14/24	>= 5.9.2 < 5.9.6
CVE-2023-41913	Critical	December 7, 2023 12/7/23	>= 5.3.0 < 5.9.12
CVE-2023-26463	Critical	April 15, 2023 4/15/23	== 5.9.9 == 5.9.8
CVE-2022-40617	High	October 31, 2022 10/31/22	< 5.9.8
CVE-2021-45079	Critical	January 31, 2022 1/31/22	>= 4.1.2 < 5.9.5
CVE-2021-41990	High	October 18, 2021 10/18/21	>= 5.6.1 < 5.9.4
CVE-2021-41991	High	October 18, 2021 10/18/21	>= 4.2.10 < 5.9.4
CVE-2019-10155	Low	June 12, 2019 6/12/19	< 5.0.0
CVE-2018-17540	Medium	October 3, 2018 10/3/18	< 5.7.1
CVE-2018-16151	High	September 26, 2018 9/26/18	>= 5.0.0 < 5.7.0 >= 4.0.0 <= 4.6.4
CVE-2018-16152	High	September 26, 2018 9/26/18	>= 5.0.0 < 5.7.0 >= 4.0.0 <= 4.6.4
CVE-2018-10811	High	June 19, 2018 6/19/18	>= 5.0.1 < 5.6.3
CVE-2018-5388	Low	May 31, 2018 5/31/18	< 5.6.3
CVE-2018-6459	Medium	February 20, 2018 2/20/18	== 5.6.1
CVE-2015-3991	High	September 7, 2017 9/7/17	== 5.2.2 == 5.3.0
CVE-2017-11185	High	August 18, 2017 8/18/17	<= 5.5.3
CVE-2017-9022	High	June 8, 2017 6/8/17	<= 5.5.2
CVE-2017-9023	High	June 8, 2017 6/8/17	<= 5.5.2
CVE-2015-8023	Medium	November 18, 2015 11/18/15	== 4.2.12 == 4.2.13 == 4.2.14 == 4.2.15 == 4.2.16 == 4.3.0 == 4.3.1 == 4.3.2 == 4.3.3 == 4.3.4 == 4.3.5 == 4.3.6 == 4.3.7 == 4.4.0 == 4.4.1 == 4.5.0 == 4.5.1 == 4.5.2 == 4.5.3 == 4.6.0 == 4.6.1 == 4.6.2 == 4.6.3 == 4.6.4 == 5.0.0 == 5.0.1 == 5.0.2 == 5.0.3 == 5.0.4 == 5.1.0 == 5.1.1 == 5.1.2 == 5.1.3 == 5.2.0 == 5.2.1 == 5.2.2 == 5.2.3 == 5.3.0 == 5.3.1 == 5.3.2 == 5.3.3
CVE-2015-4171	Low	June 10, 2015 6/10/15	== 4.3.0 == 4.3.1 == 4.3.2 == 4.3.3 == 4.3.4 == 4.3.5 == 4.3.6 == 4.3.7 == 4.4.0 == 4.4.1 == 4.5.0 == 4.5.1 == 4.5.2 == 4.5.3 == 4.6.0 == 4.6.1 == 4.6.2 == 4.6.3 == 4.6.4 == 5.0.0 == 5.0.1 == 5.0.2 == 5.0.3 == 5.0.4 == 5.1.0 == 5.1.1 == 5.1.2 == 5.1.3 == 5.2.0 == 5.2.1 == 5.2.2 == 5.2.3 == 5.3.0 == 5.3.1
CVE-2014-9221	Medium	January 7, 2015 1/7/15	== 4.5.0 == 4.5.1 == 4.5.2 == 4.5.3 == 4.6.0 == 4.6.1 == 4.6.2 == 4.6.3 == 4.6.4 == 5.0.0 == 5.0.1 == 5.0.2 == 5.0.3 == 5.0.4 == 5.1.0 == 5.1.1 == 5.1.2 == 5.1.3 == 5.2.0
CVE-2014-2891	Medium	May 7, 2014 5/7/14	== 5.0.1 == 5.1.0 == 5.0.3 == 5.0.4 == 5.0.2 <= 5.1.1 == 5.0.0
CVE-2014-2338	Medium	April 16, 2014 4/16/14	== 4.1.8 == 4.1.11 == 4.3.7 == 4.2.6 == 4.2.12 == 4.1.1 == 4.2.10 == 5.1.2 == 4.2.16 == 4.1.10 == 4.5.3 == 4.1.4 == 4.5.2 == 5.0.1 == 4.4.0 == 5.1.0 == 4.2.9 == 4.5.1 == 4.2.14 == 4.3.5 == 4.0.7 == 4.2.3 == 4.3.2 == 4.2.5 == 4.6.4 == 4.2.8 == 4.3.3 == 4.6.2 == 5.1.1 == 4.2.0 == 4.2.1 == 4.1.7 == 4.1.6 == 4.1.5 == 5.0.3 == 4.2.13 == 5.0.4 == 4.3.0 == 4.6.1 == 4.2.11 == 4.2.4 == 5.0.2 == 4.3.6 == 4.6.0 == 4.6.3 == 4.1.2 == 4.1.9 == 5.0.0 == 4.2.7 == 4.2.2 == 4.4.1 == 4.5.0 == 4.3.1 == 4.2.15 == 4.3.4 == 4.1.0 == 4.1.3
CVE-2013-6075	Medium	November 2, 2013 11/2/13	== 4.3.7 == 4.5.3 == 4.5.2 == 5.0.1 == 4.4.0 == 5.1.0 == 4.5.1 == 4.3.5 == 4.6.4 == 4.3.3 == 4.6.2 == 5.0.3 == 5.0.4 == 4.6.1 == 5.0.2 == 4.3.6 == 4.6.0 == 4.6.3 == 5.0.0 == 4.4.1 == 4.5.0 == 4.3.4
CVE-2013-6076	Medium	November 2, 2013 11/2/13	== 5.1.0 == 5.0.3 == 5.0.4 == 5.0.2
CVE-2013-5018	Low	August 28, 2013 8/28/13	== 4.1.11 == 5.0.1 == 5.0.3 == 5.0.4 == 5.0.2 == 5.0.0
CVE-2013-2054	Medium	July 9, 2013 7/9/13	== 2.4.3 == 2.5.7 == 2.4.2 == 4.1.8 == 4.1.11 == 2.6.16 == 2.5.3 == 2.8.0 == 4.2.6 == 2.8.1 == 2.4.4 == 2.6.0 == 2.3.0 == 4.2.12 == 4.1.1 == 2.7.2 == 4.2.10 == 2.1.0 == 2.1.5 == 2.0.2 == 2.8.9 == 2.8.8 == 2.8.4 == 4.2.16 == 2.7.1 == 4.1.10 == 4.1.4 == 2.6.14 == 2.6.20 == 4.0.6 == 4.2.9 == 2.5.1 == 4.2.14 == 2.4 == 2.3.1 == 2.6.2 == 2.4.0 == 4.0.7 == 2.5.5 == 2.8.3 == 4.2.3 == 4.3.2 == 2.6 == 2.0.1 == 4.2.5 == 2.1.1 == 4.2.8 == 2.6.21 == 4.3.3 == 4.2.0 == 2.6.1 == 4.2.1 == 4.1.7 == 4.1.6 == 2.7.0 == 2.8.7 == 4.1.5 == 2.4.1 == 4.0.1 == 4.0.3 == 4.2.13 == 4.0.4 == 4.3.0 == 2.8.6 == 2.0.0 == 2.5.2 == 2.1.3 == 4.2.11 == 4.2.4 == 2.1.2 == 2.8.10 == 2.6.4 == 2.5.0 == 2.5.6 == 2.7.3 == 2.5.4 == 4.1.2 == 4.0.0 == 2.4.0a == 4.1.9 == 4.2.7 == 2.3.2 == 4.2.2 == 2.8.11 == 4.0.5 == 4.3.1 == 2.1.4 == 4.2.15 == 4.1 == 4.3.4 == 4.1.0 == 2.8.5 == 4.1.3 == 2.8.2 == 2.6.3 == 4.0.2
CVE-2013-2944	Low	May 2, 2013 5/2/13	== 4.3.7 == 4.5.3 == 4.5.2 == 5.0.1 == 4.4.0 == 4.5.1 == 4.3.5 == 4.6.4 == 4.6.2 == 4.6.1 == 5.0.2 == 4.3.6 == 4.6.0 == 4.6.3 == 5.0.0 == 4.4.1 == 4.5.0
CVE-2012-2388	High	June 27, 2012 6/27/12	== 4.2.6 == 4.2.12 == 4.2.10 == 4.2.16 == 4.5.3 == 4.5.2 == 4.4.0 == 4.2.9 == 4.5.1 == 4.2.14 == 4.3.5 == 4.2.3 == 4.3.2 == 4.2.5 == 4.2.8 == 4.3.3 == 4.6.2 == 4.2.0 == 4.2.1 == 4.2.13 == 4.3.0 == 4.6.1 == 4.2.11 == 4.2.4 == 4.3.6 == 4.6.0 == 4.6.3 == 4.2.7 == 4.2.2 == 4.4.1 == 4.5.0 == 4.3.1 == 4.2.15 == 4.3.4
CVE-2010-2628	High	August 20, 2010 8/20/10	== 4.4.0 == 4.3.5 == 4.3.2 == 4.3.3 == 4.3.0 == 4.3.6 == 4.3.1 == 4.3.4
CVE-2009-2661	Medium	August 4, 2009 8/4/09	== 2.8.0 == 2.8.1 == 4.2.12 == 4.2.10 == 2.8.8 == 2.8.4 == 4.2.16 == 4.2.14 == 2.8.3 == 4.2.3 == 4.3.2 == 4.2.0 == 4.2.1 == 2.8.7 == 4.2.13 == 4.3.0 == 2.8.6 == 4.2.11 == 2.8.10 == 4.2.2 == 4.3.1 == 4.2.15 == 2.8.5 == 2.8.2
CVE-2009-2185	Medium	June 25, 2009 6/25/09	== 2.8.0 == 2.8.1 == 2.8.10 == 2.8.2 == 2.8.3 == 2.8.4 == 2.8.5 == 2.8.6 == 2.8.7 == 2.8.8 == 2.8.9 == 4.1 == 4.2.0 == 4.2.1 == 4.2.10 == 4.2.11 == 4.2.12 == 4.2.13 == 4.2.14 == 4.2.15 == 4.2.2 == 4.2.3 == 4.2.4 == 4.2.5 == 4.2.6 == 4.2.7 == 4.2.8 == 4.2.9 == 4.3.0 == 4.3.1
CVE-2009-1957	Medium	June 8, 2009 6/8/09	== 2.4.3 == 2.5.7 == 2.4.2 == 4.1.8 == 4.1.11 == 2.2.2 == 2.6.16 == 2.5.3 == 2.8.0 == 2.8.1 == 2.4.4 == 2.6.0 == 2.3.0 == 4.1.1 == 4.2.10 == 2.1.0 == 2.1.5 == 2.0.2 == 2.8.8 == 2.8.4 == 4.1.10 == 4.1.4 == 2.6.20 == 4.0.6 == 2.5.1 == 2.3.1 == 2.6.2 == 2.2.1 == 2.4.0 == 4.0.7 == 2.5.5 == 2.8.3 == 2.2.0 == 2.0.1 == 2.1.1 == 4.2.0 == 2.6.1 == 4.2.1 == 4.1.7 == 4.1.6 == 2.7.0 == 2.8.7 == 4.1.5 == 2.4.1 == 4.0.1 == 4.0.3 == 4.0.4 == 2.8.6 == 2.0.0 == 2.5.2 == 2.1.3 == 2.1.2 == 2.6.4 == 2.5.0 == 2.5.6 == 2.5.4 == 4.1.2 == 4.0.0 == 2.4.0a == 4.1.9 == 2.3.2 == 4.0.5 == 2.1.4 <= 4.3.0 == 4.1.0 == 2.8.5 == 4.1.3 == 2.8.2 == 2.6.3 == 4.0.2
CVE-2009-1958	Medium	June 8, 2009 6/8/09	== 2.4.3 == 2.5.7 == 2.4.2 == 4.1.8 == 4.1.11 == 2.2.2 == 2.6.16 == 2.5.3 == 2.8.0 == 4.2.6 == 2.8.1 == 2.4.4 == 2.6.0 == 2.3.0 == 4.2.12 == 4.1.1 == 4.2.10 == 2.1.0 == 2.1.5 == 2.0.2 <= 4.2.9 == 2.8.8 == 2.8.4 == 4.1.10 == 4.1.4 == 2.6.20 == 4.0.6 == 2.5.1 == 2.3.1 == 2.6.2 == 2.2.1 == 2.4.0 == 4.0.7 == 2.5.5 == 2.8.3 == 2.2.0 == 4.2.3 == 2.0.1 == 4.2.5 == 2.1.1 == 4.2.8 == 4.2.0 == 2.6.1 == 4.2.1 == 4.1.7 == 4.1.6 == 2.7.0 == 2.8.7 == 4.1.5 == 2.4.1 == 4.0.1 == 4.0.3 == 4.2.13 == 4.0.4 == 2.8.6 == 2.0.0 == 2.5.2 == 2.1.3 == 4.2.11 == 4.2.4 == 2.1.2 == 2.6.4 == 2.5.0 == 2.5.6 == 2.5.4 == 4.1.2 == 4.0.0 == 2.4.0a == 4.1.9 == 4.2.7 == 2.3.2 == 4.2.2 == 4.0.5 == 2.1.4 == 4.1.0 == 2.8.5 == 4.1.3 == 2.8.2 == 2.6.3 == 4.0.2
CVE-2009-0790	Medium	April 1, 2009 4/1/09	== 2.4.0 == 2.4.0a == 2.4.1 == 2.4.2 == 2.4.3 == 2.4.4 == 2.6.0 == 2.6.1 == 2.6.2 == 2.6.3 == 2.6.4 == 2.8.0 == 2.8.1 == 2.8.2 == 2.8.3 == 2.8.4 == 2.8.5 == 2.8.6 == 2.8.7 == 2.8.8 == 4.2.0 == 4.2.1 == 4.2.10 == 4.2.11 == 4.2.12 == 4.2.13 == 4.2.2 == 4.2.3 == 4.2.4 == 4.2.5 == 4.2.6 == 4.2.7 == 4.2.8 == 4.2.9
CVE-2008-4551	Medium	October 14, 2008 10/14/08	== 2.4.3 == 2.5.7 == 2.4.2 == 4.1.8 == 4.1.11 == 2.2.2 == 2.5.3 == 2.6.0 == 2.3.0 == 4.1.1 == 2.1.0 == 2.1.5 == 2.0.2 == 4.1.10 == 4.1.4 == 4.0.6 == 2.5.1 == 2.3.1 == 2.6.2 == 2.2.1 == 2.4.0 == 4.0.7 == 2.5.5 == 2.2.0 == 4.2.3 == 2.0.1 == 4.2.5 == 2.1.1 <= 4.2.6 == 4.2.0 == 2.6.1 == 4.2.1 == 4.1.7 == 4.1.6 == 2.7.0 == 4.1.5 == 2.4.1 == 4.0.1 == 4.0.3 == 4.0.4 == 2.0.0 == 2.5.2 == 2.1.3 == 4.2.4 == 2.1.2 == 2.6.4 == 2.5.0 == 2.5.6 == 2.5.4 == 4.1.2 == 4.0.0 == 2.4.0a == 4.1.9 == 2.3.2 == 4.2.2 == 4.0.5 == 2.1.4 == 4.1.0 == 4.1.3 == 2.6.3 == 4.0.2
CVE-2004-0590	High	December 6, 2004 12/6/04	<= 2.1.2

debian / strongswan

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2014-2891	Medium		May 7, 2014 5/7/14	<= 5.1.2

Showing vulnerabilities for 2 products matching "strongswan". 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.