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.

325,773

Total vulnerabilities in the database

Vulnerabilities for products matching "client_security"

Found 3 matching products. Filters apply to all results.

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

symantec / client_security

27 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2010-0107	High	February 23, 2010 2/23/10	== 3.0 == 3.0.1.1000 == 3.0.1.1001 == 3.0.1.1007 == 3.0.1.1008 == 3.0.1.1009 == 3.0.2 == 3.0.2.2000 == 3.0.2.2001 == 3.0.2.2002 == 3.0.2.2010 == 3.0.2.2011 == 3.0.2.2020 == 3.0.2.2021 == 3.1 == 3.1-mr4 == 3.1-mr5 == 3.1-mr6 == 3.1.0.396 == 3.1.0.401 == 3.1.396 == 3.1.400 == 3.1.401
CVE-2010-0106	Low	February 19, 2010 2/19/10	== 3.0 == 3.0-mr1 == 3.0-mr2 == 3.0.0.359 == 3.0.1.1000 == 3.0.1.1007 == 3.0.1.1008 == 3.0.2 == 3.0.2.2000 == 3.0.2.2001 == 3.0.2.2010 == 3.0.2.2011 == 3.0.2.2020 == 3.0.2.2021 == 3.1 == 3.1-mr4 == 3.1-mr5 == 3.1-mr7 == 3.1.0.396 == 3.1.0.401 == 3.1.394 == 3.1.400 == 3.1.401
CVE-2010-0108	High	February 19, 2010 2/19/10	== 3.0 == 3.0-mr1 == 3.0-mr2 == 3.0.0.359 == 3.0.1.1000 == 3.0.1.1007 == 3.0.1.1008 == 3.0.2 == 3.0.2.2000 == 3.0.2.2001 == 3.0.2.2010 == 3.0.2.2011 == 3.0.2.2020 == 3.0.2.2021 == 3.1 == 3.1-mr4 == 3.1-mr5 == 3.1-mr7 == 3.1.0.396 == 3.1.0.401 == 3.1.394 == 3.1.400 == 3.1.401
CVE-2009-3104	Low	September 8, 2009 9/8/09	== 3.0 == 3.1-mr6 == 3.1-mr7 == 3.0-mr1 == 2.0 == 3.0-mr2 == 3.1 == 3.1-mr4 == 2.0-mr6 == 3.1-mr5
CVE-2009-1432	Medium	April 30, 2009 4/30/09	== 3.1 == 3.1-maintenance_release7
CVE-2009-1429	High	April 29, 2009 4/29/09	<= 3.1 == 2.0 == 3.0 == 3.0.0.359 == 3.0.1.1000 == 3.0.1.1001 == 3.0.1.1007 == 3.0.1.1008 == 3.0.1.1009 == 3.0.2 == 3.0.2.2000 == 3.0.2.2001 == 3.0.2.2002 == 3.0.2.2010 == 3.0.2.2011 == 3.0.2.2020 == 3.0.2.2021
CVE-2009-1430	High	April 29, 2009 4/29/09	<= 3.1 == 2.0 == 3.0 == 3.0.0.359 == 3.0.1.1000 == 3.0.1.1001 == 3.0.1.1007 == 3.0.1.1008 == 3.0.1.1009 == 3.0.2 == 3.0.2.2000 == 3.0.2.2001 == 3.0.2.2002 == 3.0.2.2010 == 3.0.2.2011 == 3.0.2.2020 == 3.0.2.2021
CVE-2009-1431	High	April 29, 2009 4/29/09	<= 2.0 >= 3.0 <= 3.1
CVE-2007-0447	High	October 5, 2007 10/5/07	== 2.0 == 2.0-build_9.0.0.338 == 2.0.1_build_9.0.1.1000-mr1 == 2.0.2_build_9.0.2.1000-mr2 == 2.0.3_build_9.0.3.1000-mr3 == 2.0.4 == 2.0.4-mr4_build1000 == 2.0.5_build_1100_mp1-mr5 == 2.0.6-mr6 == 3.0 == 3.0.0.359 == 3.0.1.1000 == 3.0.1.1001 == 3.0.1.1007 == 3.0.1.1008 == 3.0.2.2000 == 3.0.2.2001 == 3.0.2.2002 == 3.0.2.2010 == 3.0.2.2011 == 3.0.2.2020 == 3.0.2.2021 == 3.1 == 3.1.394 == 3.1.396 == 3.1.400 == 3.1.401
CVE-2007-3699	High	October 5, 2007 10/5/07	== 2.0 == 2.0-build_9.0.0.338 == 2.0.1_build_9.0.1.1000-mr1 == 2.0.2_build_9.0.2.1000-mr2 == 2.0.3_build_9.0.3.1000-mr3 == 2.0.4 == 2.0.4-mr4_build1000 == 2.0.5_build_1100_mp1-mr5 == 2.0.6-mr6 == 3.0 == 3.0.0.359 == 3.0.1.1000 == 3.0.1.1001 == 3.0.1.1007 == 3.0.1.1008 == 3.0.2.2000 == 3.0.2.2001 == 3.0.2.2002 == 3.0.2.2010 == 3.0.2.2011 == 3.0.2.2020 == 3.0.2.2021 == 3.1 == 3.1.394 == 3.1.396 == 3.1.400 == 3.1.401
CVE-2007-3800	Medium	July 16, 2007 7/16/07	== 2.1 == 2.0 <= 3.0
CVE-2007-3771	Low	July 15, 2007 7/15/07	== 3.0 == 3.0.1.1009 == 3.0.2.2021 == 3.0.1.1000 == 3.0.2.2002 == 3.0.2.2011 == 3.0.2 == 3.0.2.2001 == 2.0 == 3.0.2.2000 == 3.0.1.1007
CVE-2007-3673	Medium	July 15, 2007 7/15/07	== 3.0 == 2.0 == 3.1
CVE-2007-3095	High	June 6, 2007 6/6/07	== 3.1.396 == 3.1.401 == 3.1.400 == 3.1 == 3.1.394
CVE-2007-3021	High	June 5, 2007 6/5/07	== 3.1.396 == 3.1.401 == 3.1.400 == 3.1 == 3.1.394
CVE-2007-3022	Low	June 5, 2007 6/5/07	== 3.1.396 == 3.1.401 == 3.1.400 == 3.1 == 3.1.394
CVE-2007-1793	Low	April 2, 2007 4/2/07	== 3.0 == 3.0.0.359 == 3.0.1.1000 == 3.0.1.1001 == 3.0.1.1007 == 3.0.1.1008 == 3.0.1.1009 == 3.0.2 == 3.0.2.2000 == 3.0.2.2001 == 3.0.2.2002 == 3.0.2.2010 == 3.0.2.2011 == 3.0.2.2020 == 3.0.2.2021 == 3.1 == 3.1.0.396 == 3.1.0.401 == 3.1.394 == 3.1.396 == 3.1.400 == 3.1.401
CVE-2007-1476	Low	March 16, 2007 3/16/07	== 3.0 == 3.0.1.1009 == 2.0.6 == 3.0.2.2020 == 2.0.6-mr6 == 2.1 == 2.0-build_9.0.0.338 == 3.0.2.2021 == 2.0.1_build_9.0.1.1000-mr1 == 2.0.3_build_9.0.3.1000-mr3 == 3.0.1.1000 == 2.0.4 == 3.1.0.401 == 3.0.2.2002 == 3.0.1.1008 == 2.0.5_build_1100 == 3.0.2.2011 == 2.0.4-mr4_build1000 == 3.0.2 == 3.1.396 == 2.0 == 2.0.5_build_1100_mp1-mr5 == 2.0.5 == 3.0.1.1001 == 3.0.2.2001 == 2.0.3 == 3.1.401 == 3.0.0.359 == 3.1.400 == 3.0.2.2010 == 2.0_scf_7.1 == 3.1 == 3.1.0.396 == 3.0.2.2000 == 3.1.394 == 3.0.1.1007 == 2.0.2 == 2.0_stm_build_9.0.0.338 == 2.0.1 == 2.0.2_build_9.0.2.1000-mr2
CVE-2006-3455	Low	October 23, 2006 10/23/06	== 1.1 == 1.1_stm_b8.1.0.825a == 1.1.1 == 1.1.1_build_393 == 1.1.1_mr1_build_8.1.1.314a == 1.1.1_mr2_build_8.1.1.319 == 1.1.1_mr3_build_8.1.1.323 == 1.1.1_mr4_build_8.1.1.329 == 1.1.1_mr5_build_8.1.1.336 == 1.1.1_mr6_b8.1.1.266 == 2.0 == 2.0_scf_7.1 == 2.0_stm_build_9.0.0.338 == 2.0.1 == 2.0.1_build_9.0.1.1000-mr1 == 2.0.2 == 2.0.2_build_9.0.2.1000-mr2 == 2.0.3 == 2.0.3_build_9.0.3.1000-mr3
CVE-2006-4855	Low	September 19, 2006 9/19/06	== 1.0 == 1.0_build_8.01.9374 == 1.0.0_b8.01.9378 == 1.0.1 == 1.0.1_build_8.01.425a-mr1 == 1.0.1_build_8.01.429c-mr2 == 1.0.1_build_8.01.434-mr3 == 1.0.1_build_8.01.437 == 1.0.1_build_8.01.446-mr4 == 1.0.1_build_8.01.457-mr5 == 1.0.1_build_8.01.460-mr6 == 1.0.1_build_8.01.464-mr7 == 1.0.1_build_8.01.471-mr8 == 1.0.1_build_8.01.501-mr9 == 1.1 == 1.1_stm_b8.1.0.825a == 1.1.1 == 1.1.1_build_393 == 1.1.1_mr1_build_8.1.1.314a == 1.1.1_mr2_build_8.1.1.319 == 1.1.1_mr3_build_8.1.1.323 == 1.1.1_mr4_build_8.1.1.329 == 1.1.1_mr5_build_8.1.1.336 == 1.1.1_mr6_b8.1.1.266 == 2.0 == 2.0_scf_7.1 == 2.0_stm_build_9.0.0.338 == 2.0.1_build_9.0.1.1000-mr1 == 2.0.2_build_9.0.2.1000-mr2 == 2.0.3_build_9.0.3.1000-mr3 == 2.0.5_build_1100 == 3.0 == 3.1
CVE-2006-4802	Low	September 14, 2006 9/14/06	== 1.0.1 == 1.0.1_build_8.01.460-mr6 == 1.0.1_build_8.01.446-mr4 == 1.6 == 2.0.4 == 1.2 == 1.1.1_mr1_build_8.1.1.314a == 1.1.1 == 1.7 == 1.0.1_build_8.01.471-mr8 == 1.0.1_build_8.01.457-mr5 == 1.1 == 1.8 == 1.1.1_mr3_build_8.1.1.323 == 1.1.1_mr2_build_8.1.1.319 == 1.1.1_mr5_build_8.1.1.336 == 1.9 == 1.0.1_build_8.01.437 == 1.4 == 2.0 == 2.0.3 == 1.1.1_mr4_build_8.1.1.329 == 1.0.1_build_8.01.434-mr3 == 1.5 == 1.3 == 2.0.2 == 2.0.1 == 1.0.1_build_8.01.464-mr7 == 1.0
CVE-2006-3454	High	September 14, 2006 9/14/06	== 3.0 == 1.0.1 == 2.0.4 == 1.1.1 == 1.1 == 2.0 == 2.0.3 == 2.0.2 == 2.0.1 == 1.0
CVE-2006-2630	High	May 27, 2006 5/27/06	== 3.0 == 3.0.2.2020 == 3.1.400 == 3.0.2.2010 == 3.1 == 3.1.394
CVE-2005-0249	High	February 8, 2005 2/8/05	== 1.0.1_build_8.01.434-mr3 == 1.0.1_build_8.01.437 == 1.0.1_build_8.01.446-mr4 == 1.0.1_build_8.01.457-mr5 == 1.0.1_build_8.01.460-mr6 == 1.0.1_build_8.01.464-mr7 == 1.0.1_build_8.01.471-mr8 == 1.1.1_mr1_build_8.1.1.314a == 1.1.1_mr2_build_8.1.1.319 == 1.1.1_mr3_build_8.1.1.323 == 1.1.1_mr4_build_8.1.1.329 == 1.1.1_mr5_build_8.1.1.336
CVE-2004-0375	Medium	August 18, 2004 8/18/04	== 1.1 == 1.0
CVE-2004-0444	High	July 7, 2004 7/7/04	== 1.6 == 1.2 == 1.7 == 1.1 == 1.8 == 1.9 == 1.4 == 2.0 == 1.5 == 1.3 == 1.0
CVE-2004-0445	Low	July 7, 2004 7/7/04	== 1.6 == 1.2 == 1.7 == 1.1 == 1.8 == 1.9 == 1.4 == 2.0 == 1.5 == 1.3 == 1.0

f-secure / client_security

9 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2023-49322	High	November 27, 2023 11/27/23	== 15.00
CVE-2023-49321	Medium	November 27, 2023 11/27/23	== 15.00
CVE-2023-43767	High	September 22, 2023 9/22/23	== 15.00
CVE-2023-43766	High	September 22, 2023 9/22/23	== 15.00
CVE-2023-43765	High	September 22, 2023 9/22/23	== 15.00
CVE-2023-43761	High	September 22, 2023 9/22/23	== 15.00
CVE-2023-43760	High	September 22, 2023 9/22/23	== 15.00
CVE-2019-11644	Medium	May 17, 2019 5/17/19	< 14.10
CVE-2009-1782	Medium	May 22, 2009 5/22/09	<= 8.0

withsecure / client_security

12 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-4454	High	May 22, 2024 5/22/24	== 15
CVE-2024-23764	Medium	February 8, 2024 2/8/24	== 15
CVE-2023-47172	High	November 20, 2023 11/20/23	== 15
CVE-2023-47264	High	November 16, 2023 11/16/23	== 15
CVE-2023-47263	High	November 16, 2023 11/16/23	== 15
CVE-2023-42525	High	September 18, 2023 9/18/23	== 15
CVE-2023-42524	High	September 18, 2023 9/18/23	== 15
CVE-2023-42523	High	September 18, 2023 9/18/23	== 15
CVE-2023-42522	High	September 18, 2023 9/18/23	== 15
CVE-2023-42521	High	September 18, 2023 9/18/23	== 15
CVE-2023-42520	High	September 18, 2023 9/18/23	== 15
CVE-2023-42526	High	September 18, 2023 9/18/23	== 15

Showing vulnerabilities for 3 products matching "client_security". 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.