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 "norton_antivirus"

Found 1 matching product.

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

symantec / norton_antivirus

67 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2016-5311	High	January 9, 2020 1/9/20	< 22.7
CVE-2018-12238	Low	November 29, 2018 11/29/18	< 22.15
CVE-2018-12239	Low	November 29, 2018 11/29/18	< 22.15
CVE-2016-3646	High	June 30, 2016 6/30/16	*
CVE-2016-3645	High	June 30, 2016 6/30/16	*
CVE-2016-3644	High	June 30, 2016 6/30/16	*
CVE-2016-2211	High	June 30, 2016 6/30/16	*
CVE-2016-2210	High	June 30, 2016 6/30/16	*
CVE-2016-2209	High	June 30, 2016 6/30/16	*
CVE-2016-2207	High	June 30, 2016 6/30/16	*
CVE-2010-3497	Medium	August 22, 2012 8/22/12	== 2011
CVE-2010-0107	High	February 23, 2010 2/23/10	== 2008 == 2007 == 2006
CVE-2009-3104	Low	September 8, 2009 9/8/09	== 2008 == 2007 == 2006 == 2005
CVE-2008-0312	High	April 8, 2008 4/8/08	== 2006 == 2007 == 2008
CVE-2008-0313	Medium	April 8, 2008 4/8/08	== 2008 == 2007 == 2006
CVE-2007-5829	Medium	November 5, 2007 11/5/07	== 9.0.2 == 9.0.3 == 10.1 == 10.0 == 9.0.1 == 9.0
CVE-2007-0447	High	October 5, 2007 10/5/07	* == 10.0 == 10.0.0 == 10.0.0.359 == 10.0.1 == 10.0.1.1000 == 10.0.1.1007 == 10.0.1.1008 == 10.0.2.2000 == 10.0.2.2001 == 10.0.2.2002 == 10.0.2.2010 == 10.0.2.2011 == 10.0.2.2020 == 10.0.2.2021 == 10.1 == 10.1.394 == 10.1.396 == 10.1.4 == 10.1.4-mr4_mp1_build4010 == 10.1.4.4010 == 10.1.400 == 10.1.401 == 10.9.1 == 2004 == 2005 == 2005-11.0 == 2005-11.0.9 == 2006 == 9.0 == 9.0.0 == 9.0.0.338 == 9.0.1 == 9.0.1.1.1000 == 9.0.2 == 9.0.2.1000 == 9.0.3 == 9.0.3.1000 == 9.0.4 == 9.0.4-mr4_build_1000 == 9.0.5 == 9.0.5.1100 == 9.0.6.1000
CVE-2007-3699	High	October 5, 2007 10/5/07	* == 10.0 == 10.0.0 == 10.0.0.359 == 10.0.1 == 10.0.1.1000 == 10.0.1.1007 == 10.0.1.1008 == 10.0.2.2000 == 10.0.2.2001 == 10.0.2.2002 == 10.0.2.2010 == 10.0.2.2011 == 10.0.2.2020 == 10.0.2.2021 == 10.1 == 10.1.394 == 10.1.396 == 10.1.4 == 10.1.4-mr4_mp1_build4010 == 10.1.4.4010 == 10.1.400 == 10.1.401 == 10.9.1 == 2004 == 2005 == 2005-11.0 == 2005-11.0.9 == 2006 == 9.0 == 9.0.0 == 9.0.0.338 == 9.0.1 == 9.0.1.1.1000 == 9.0.2 == 9.0.2.1000 == 9.0.3 == 9.0.3.1000 == 9.0.4 == 9.0.4-mr4_build_1000 == 9.0.5 == 9.0.5.1100 == 9.0.6.1000
CVE-2007-2955	Medium	August 9, 2007 8/9/07	== 2006
CVE-2007-3800	Medium	July 16, 2007 7/16/07	<= 10.1 == 10.0 == 9.0
CVE-2007-3771	Low	July 15, 2007 7/15/07	== 10.0 == 10.0.1.1000 == 10.0.1.1007 == 10.0.2.2000 == 10.0.2.2001 == 10.0.2.2002 == 10.0.2.2010 == 10.0.2.2011 == 10.0.2.2020 == 10.0.2.2021 == 9.0 == 9.0.0.338 == 9.0.1 == 9.0.1.1.1000 == 9.0.1.1000 == 9.0.2 == 9.0.2.1000 == 9.0.3.1000 == 9.0.4 == 9.0.5 == 9.0.5.1100
CVE-2007-3673	Medium	July 15, 2007 7/15/07	== 10.0 == 10.1 == 2005 == 2006 == 9.0 == 9.0.0.338 == 9.0.1 == 9.0.1.1.1000 == 9.0.1.1000 == 9.0.2 == 9.0.2.1000 == 9.0.3.1000 == 9.0.4 == 9.0.5 == 9.0.5.1100
CVE-2007-3095	High	June 6, 2007 6/6/07	== 10.1 == 10.1.400 == 10.1.401 == 10.1.396 == 10.0.2.2021
CVE-2007-3021	High	June 5, 2007 6/5/07	== 10.1 == 10.1.400 == 10.1.401 == 10.1.396 == 10.0.2.2021
CVE-2007-3022	Low	June 5, 2007 6/5/07	== 10.1 == 10.1.400 == 10.1.401 == 10.1.396 == 10.0.2.2021
CVE-2006-3456	High	May 11, 2007 5/11/07	== 2006 == 2005
CVE-2007-1793	Low	April 2, 2007 4/2/07	== 2008 == 2007 == 2006 == 2004 == 2005
CVE-2007-1476	Low	March 16, 2007 3/16/07	== 10.0 == 10.0.1.1000 == 10.0.1.1007 == 10.0.1.1008 == 10.0.2.2000 == 10.0.2.2001 == 10.0.2.2002 == 10.0.2.2010 == 10.0.2.2011 == 10.0.2.2020 == 10.0.2.2021 == 10.1 == 10.1.394 == 10.1.396 == 10.1.4 == 10.1.4.4010 == 10.1.400 == 10.1.401 == 2005 == 2006 == 3.0 == 9.0 == 9.0.0.338 == 9.0.1 == 9.0.1.1.1000 == 9.0.1.1000 == 9.0.2 == 9.0.2.1000 == 9.0.3.1000 == 9.0.4 == 9.0.5 == 9.0.5.1100 == 9.0.6.1000
CVE-2006-6490	High	February 22, 2007 2/22/07	== 2006
CVE-2006-3455	Low	October 23, 2006 10/23/06	== 8.01.434 == 8.01.437 == 8.01.446 == 8.01.457 == 8.01.460 == 8.01.464 == 8.01.471 == 8.1 == 8.1.0.825a == 8.1.1 == 8.1.1_build393 == 8.1.1_build8.1.1.314a == 8.1.1.319 == 8.1.1.323 == 8.1.1.329 == 8.1.1.366 == 8.1.1.377 == 9.0.1 == 9.0.1.1.1000 == 9.0.1.1000 == 9.0.2 == 9.0.2.1000
CVE-2006-5403	Medium	October 19, 2006 10/19/06	*
CVE-2006-5404	Low	October 19, 2006 10/19/06	*
CVE-2006-4855	Low	September 19, 2006 9/19/06	== 10.1 == 2004 == 9.0.2.1000 == 9.0.3.1000 == 8.01.460 == 2007 == 10.0.2.2011 == 10.0.2.2010 == 10.0 == 8.01.437 == 2003 == 8.1.1_build393 == 8.1.1.323 == 8.01.457 == 8.1.1_build8.1.1.314a == 9.0.1.1.1000 == 8.1.0.825a == 9.0.5.1100 == 2.1 == 8.01.446 == 8.01.464 == 10.0.2.2001 == 8.0.1.425a == 10.0.2.2020 == 8.1.1.319 == 8.01.434 == 8.0.1.425c == 8.0.1.501 == 8.01.471 == 9.0.4 == 2006 == 8.0.1.9378 == 9.0.0.338 == 10.0.2.2000 == 8.0 == 2005 == 8.1 == 8.1.1.329 == 10.0.2.2021 == 8.1.1.377 == 8.0.1.9374 == 9.0 == 8.1.1 == 9.0.5 == 8.0.1 == 10.0.2.2002 == 8.1.1.366
CVE-2006-4802	Low	September 14, 2006 9/14/06	== 9.0.2 == 8.1.1.323 == 8.1.1_build8.1.1.314a == 9.0.1.1.1000 == 9.0.1 == 9.0.1.1000 == 8.1.1.319 == 9.0.4 == 8.1 == 8.1.1.329 == 9.0
CVE-2006-3454	High	September 14, 2006 9/14/06	== 9.0.2 == 10.0 == 9.0.1 == 8.1 == 9.0
CVE-2006-2630	High	May 27, 2006 5/27/06	== 10.1 == 10.1.400 == 10.0.2.2010 == 10.0 == 10.0.2.2020 == 10.0.2.2021
CVE-2006-1836	Medium	April 19, 2006 4/19/06	== 9.0.0 == 9.0.2 == 10.0.0 == 9.0.3 == 10.0.1 == 10.0 == 10.9.1 == 9.0.1
CVE-2005-3270	High	October 21, 2005 10/21/05	== 9.0.3
CVE-2005-2759	High	October 20, 2005 10/20/05	== 9.0.3
CVE-2005-2766	Low	September 2, 2005 9/2/05	== 9.0.1.1.1000 == 9.0.4
CVE-2005-2017	High	August 30, 2005 8/30/05	== 9.0.1.1000
CVE-2005-0922	Medium	May 2, 2005 5/2/05	== 2.1 == 2005
CVE-2005-0923	Low	May 2, 2005 5/2/05	== 2.1 == 2005
CVE-2005-1346	Low	May 2, 2005 5/2/05	== 2005_11.0.0
CVE-2005-0249	High	February 8, 2005 2/8/05	== 2.18_build_83 == 2004 == 8.01.434 == 8.01.437 == 8.01.446 == 8.01.457 == 8.01.460 == 8.01.464 == 8.01.471 == 8.1.1_build8.1.1.314a == 8.1.1.319 == 8.1.1.323 == 8.1.1.329 == 9.0
CVE-2004-2147	Medium	December 31, 2004 12/31/04	== 2001 == professional_2002 == corporate_7.61 == corporate_7.2 == corporate_7.51 == 2.1 == professional_2003 == corporate_7.0 == corporate_7.6 == professional_2004 == professional_2001 == corporate_7.5 == corporate_8.0 == 2002 == 2003 == corporate_7.60.build_926
CVE-2004-0920	Medium	November 3, 2004 11/3/04	<= 2.1
CVE-2004-0487	High	August 18, 2004 8/18/04	== 2.1
CVE-2004-0683	Medium	August 6, 2004 8/6/04	== 2003 == 2002
CVE-2003-0994	High	February 3, 2004 2/3/04	== 2001 == 3.0 == 2002 == 2003 == 2.1 == 2004

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.