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.

383,371

Total vulnerabilities in the database

Vulnerabilities for products matching "backup_exec"

Found 3 matching products. Filters apply to all results.

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

symantec_veritas / backup_exec

11 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2006-4128	Medium	August 14, 2006 8/14/06	`= 9.1` `= 9.1_build9.1.4691` `= 9.2` `= 10.0` `= 10.0_build10.0.5484` `= 10.0_build10.0.5520` `= 10.1` `= 10.1.325.6301` `= 10.1.326.1401` `= 10.1.326.2501` `= 10.1.326.3301` `= 10.1.327.401` `= 10.1_build10.1.5629`
CVE-2006-1297	Medium	March 19, 2006 3/19/06	`= netware_server_9.1` `= netware_server_9.2`
CVE-2006-1298	Medium	March 19, 2006 3/19/06	`= 9.1` `= 10.0`
CVE-2005-2611	High	August 17, 2005 8/17/05	`= netware_servers_9.0.4019` `= netware_servers_9.0.4170` `= netware_servers_9.0.4172` `= netware_servers_9.0.4174` `= netware_servers_9.0.4202` `= netware_servers_9.1.306` `= netware_servers_9.1.307` `= netware_servers_9.1.1067_.2` `= netware_servers_9.1.1067_.3` `= netware_servers_9.1.1127_.1` `= netware_servers_9.1.1151_.1` `= netware_servers_9.1.1152` `= netware_servers_9.1.1152_.4` `= netware_servers_9.1.1154` `= netware_servers_9.1.1156` `= windows_servers_8.6` `= windows_servers_9.0` `= windows_servers_9.0_rev._4367` `= windows_servers_9.0_rev._4367_sp1` `= windows_servers_9.0_rev._4454` `= windows_servers_9.0_rev._4454_sp1` `= windows_servers_9.1` `= windows_servers_9.1_rev._4691` `= windows_servers_9.1_rev._4691_sp2` `= windows_servers_10.0_rev._5484` `= windows_servers_10.0_rev._5484_sp1` `= windows_servers_10.0_rev._5520`
CVE-2005-2079	High	August 2, 2005 8/2/05	`= 9.0_rev.4367` `= 9.0_rev.4454` `= 9.1_rev.4691` `= 10.0_rev.5484`
CVE-2005-2080	High	June 29, 2005 6/29/05	`= 9.0` `= 9.0.4019` `= 9.0.4170` `= 9.0.4172` `= 9.0.4174` `= 9.0.4202` `= 9.1` `= 9.1.306` `= 9.1.307` `= 9.1.1067.2` `= 9.1.1067.3` `= 9.1.1127.1` `= 9.1.1151.1` `= 9.1.1152` `= 9.1.1152.4` `= 9.1.1154` `= 10.0`
CVE-2005-2051	High	June 28, 2005 6/28/05	`= 9.0` `= 9.0_rev.4367` `= 9.0_rev.4454` `= 9.1` `= 9.1_rev.4691` `= 10.0` `= 10.0_rev.5484`
CVE-2005-0771	High	June 23, 2005 6/23/05	`= 9.0_rev.4367` `= 9.0_rev.4454` `= 9.1_rev.4691` `= 10.0_rev.5484`
CVE-2005-0773	High	June 18, 2005 6/18/05	`= 9.0.4019` `= 9.0.4170` `= 9.0.4172` `= 9.0.4174` `= 9.0.4202` `= 9.0_rev.4367` `= 9.0_rev.4367_sp1` `= 9.0_rev.4454` `= 9.0_rev.4454_sp1` `= 9.1.306` `= 9.1.307` `= 9.1.1067.2` `= 9.1.1067.3` `= 9.1.1127.1` `= 9.1.1151.1` `= 9.1.1152` `= 9.1.1152.4` `= 9.1.1154` `= 9.1_rev.4691` `= 9.1_rev.4691_sp2` `= 10.0_rev.5484` `= 10.0_rev.5484_sp1`
CVE-2004-1172	High	January 10, 2005 1/10/05	`= 8.0` `= 8.5` `= 8.6` `= 9.0` `= 9.1`
CVE-2002-1117	Medium	October 4, 2002 10/4/02	`<= 8.5`

symantec / backup_exec

5 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2013-4575	High	August 5, 2013 8/5/13	`= 2010` `= 2010-r3` `= 2012`
CVE-2013-4676	Medium	August 5, 2013 8/5/13	`= 2010_r3` `= 2010_r3-sp1` `= 2010_r3-sp2` `= 2012`
CVE-2013-4677	Medium	August 5, 2013 8/5/13	`= 2010` `= 2010_r3-sp1` `= 2010_r3-sp2` `= 2012` `= 2012-sp1`
CVE-2013-4678	Low	August 5, 2013 8/5/13	`= 2010` `= 2010_r3-sp1` `= 2010_r3-sp2` `= 2012` `= 2012-sp1`
CVE-2011-0546	Medium	May 31, 2011 5/31/11	`= 11.0` `= 12.0` `= 12.5` `= 13.0` `= 13.0-r2`

veritas / backup_exec

8 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2024-33673	High	April 26, 2024 4/26/24	`>= 21.0, < 23.0`
CVE-2024-33671	High	April 26, 2024 4/26/24	`>= 21.0, < 23.0`
CVE-2021-27876	High	March 1, 2021 3/1/21	`< 21.2`
CVE-2021-27877	High	March 1, 2021 3/1/21	`< 21.2`
CVE-2021-27878	High	March 1, 2021 3/1/21	`< 21.2`
CVE-2020-36167	Critical	January 6, 2021 1/6/21	`>= 20.0, < 20.0.1188.2734` `>= 21.0, < 21.0.1200.1217`
CVE-2017-8895	High	May 10, 2017 5/10/17	`< 16.0.1142.1327` `< 14.1.1786.1126` `< 14.2.1180.3160`
CVE-2005-0772	High	June 28, 2005 6/28/05	`>= 9.0, <= 10.0` `>= 9.0.4019, <= 9.1.307`

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