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.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "service_manager"

Found 5 matching products. Filters apply to all results.

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

hp / service_manager

26 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2016-4371	Medium	June 19, 2016 6/19/16	== 9.41 == 9.33 == 9.35 == 9.32 == 9.30 == 9.40 == 9.34 == 9.31
CVE-2016-2025	Medium	May 30, 2016 5/30/16	== 9.41 == 9.33 == 9.35 == 9.32 == 9.30 == 9.40 == 9.34 == 9.31
CVE-2016-1998	High	March 22, 2016 3/22/16	== 9.41 == 9.33 == 9.35 == 9.32 == 9.30 == 9.40 == 9.34 == 9.31
CVE-2014-2632	High	August 23, 2014 8/23/14	== 7.21 == 9.33 == 9.32 == 9.30 == 9.21 == 9.31
CVE-2014-2633	Medium	August 23, 2014 8/23/14	== 7.21 == 9.33 == 9.32 == 9.30 == 9.21 == 9.31
CVE-2014-2634	High	August 23, 2014 8/23/14	== 7.21 == 9.33 == 9.32 == 9.30 == 9.21 == 9.31
CVE-2013-6222	Low	August 23, 2014 8/23/14	== 7.21 == 9.33 == 9.32 == 9.30 == 9.21 == 9.31
CVE-2013-6202	Medium	February 24, 2014 2/24/14	== 9.33 == 9.32 == 9.30 == 9.31
CVE-2013-6197	Medium	December 29, 2013 12/29/13	== 9.20 == 9.21
CVE-2013-6198	Low	December 29, 2013 12/29/13	== 9.20 == 9.21
CVE-2013-4844	High	November 29, 2013 11/29/13	== 9.32 == 9.30 == 7.11 == 9.21 == 9.31
CVE-2013-4831	Medium	October 16, 2013 10/16/13	== 9.32 == 9.30 == 9.31
CVE-2013-4832	Low	October 16, 2013 10/16/13	== 9.32 == 9.30 == 9.31
CVE-2013-4833	Low	October 16, 2013 10/16/13	== 9.32 == 9.30 == 9.31
CVE-2013-4830	High	October 16, 2013 10/16/13	== 9.32 == 9.30 == 9.31
CVE-2013-4808	High	August 18, 2013 8/18/13	== 9.30 == 7.11 == 9.21 == 9.31
CVE-2013-2336	Medium	June 14, 2013 6/14/13	== 9.30 == 7.11 == 9.21 == 9.31
CVE-2013-2337	Low	June 14, 2013 6/14/13	== 9.30 == 7.11 == 9.21 == 9.31
CVE-2011-1859	Medium	June 14, 2011 6/14/11	== 9.20 == 7.02 == 7.11 == 9.21
CVE-2011-1860	Medium	June 14, 2011 6/14/11	== 9.20 == 7.02 == 7.11 == 9.21
CVE-2011-1861	High	June 14, 2011 6/14/11	== 9.20 == 7.02 == 7.11 == 9.21
CVE-2011-1862	Low	June 14, 2011 6/14/11	== 9.20 == 7.02 == 7.11 == 9.21
CVE-2011-1863	High	June 14, 2011 6/14/11	== 9.20 == 7.02 == 7.11 == 9.21
CVE-2011-1857	High	June 14, 2011 6/14/11	== 9.20 == 7.02 == 7.11 == 9.21
CVE-2011-1858	Low	June 14, 2011 6/14/11	== 9.20 == 7.02 == 7.11 == 9.21
CVE-2008-4415	High	November 17, 2008 11/17/08	<= 7.0

microfocus / service_manager

16 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2020-11845	Medium	May 19, 2020 5/19/20	>= 9.50 <= 9.63
CVE-2020-9518	Medium	March 16, 2020 3/16/20	>= 9.50 <= 9.62
CVE-2020-9519	Medium	March 16, 2020 3/16/20	>= 9.40 <= 9.63
CVE-2020-9517	Medium	March 9, 2020 3/9/20	== 9.50 == 9.60
CVE-2019-11663	Medium	September 18, 2019 9/18/19	>= 9.30 <= 9.62
CVE-2019-11664	Medium	September 18, 2019 9/18/19	>= 9.30 <= 9.62
CVE-2019-11661	High	September 18, 2019 9/18/19	>= 9.30 <= 9.62
CVE-2019-11662	Low	September 18, 2019 9/18/19	>= 9.30 <= 9.62
CVE-2019-11665	High	September 17, 2019 9/17/19	>= 9.30 <= 9.62
CVE-2019-11666	High	September 17, 2019 9/17/19	>= 9.30 <= 9.62
CVE-2019-11667	High	September 17, 2019 9/17/19	>= 9.41 <= 9.62
CVE-2019-11668	High	September 10, 2019 9/10/19	== 9.30 == 9.31 == 9.32 == 9.33 == 9.34 == 9.35 == 9.40 == 9.41 == 9.50 == 9.51 == 9.52 == 9.60 == 9.61 == 9.62
CVE-2019-11669	High	September 10, 2019 9/10/19	== 9.61 == 9.60-p1 == 9.62
CVE-2019-11646	High	June 3, 2019 6/3/19	== 9.30 == 9.31 == 9.32 == 9.33 == 9.34 == 9.35 == 9.40 == 9.41 == 9.50 == 9.51 == 9.52 == 9.60 == 9.61
CVE-2018-18591	Low	November 13, 2018 11/13/18	== 9.30 == 9.31 == 9.32 == 9.33 == 9.34 == 9.35 == 9.40 == 9.41 == 9.50 == 9.51
CVE-2018-6494	Medium	May 22, 2018 5/22/18	== 9.30 == 9.31 == 9.32 == 9.33 == 9.34 == 9.35 == 9.40 == 9.41 == 9.50 == 9.51

intel / service_manager

4 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2020-8674	Medium	June 15, 2020 6/15/20	>= 14.0 < 14.0.33 >= 12.0 < 12.0.64 >= 11.20 < 11.22.77 >= 11.10 < 11.12.77 >= 11.0 < 11.8.77
CVE-2020-0594	Critical	June 15, 2020 6/15/20	>= 12.0 < 12.0.64 >= 11.20 < 11.22.77 >= 11.10 < 11.12.77 >= 11.0 < 11.8.77
CVE-2020-0595	Critical	June 15, 2020 6/15/20	>= 12.0 < 12.0.64 >= 11.20 < 11.22.77 >= 11.10 < 11.12.77 >= 11.0 < 11.8.77
CVE-2020-0596	High	June 15, 2020 6/15/20	>= 12.0 < 12.0.64 >= 11.20 < 11.22.77 >= 11.10 < 11.12.77 >= 11.0 < 11.8.77

easyvista / service_manager

5 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-38489	Low	January 10, 2023 1/10/23	== 2022.1.109.0.03 == 2020.2.125.3
CVE-2022-38490	Critical	January 10, 2023 1/10/23	== 2022.1.109.0.03 == 2020.2.125.3
CVE-2022-38491	High	January 10, 2023 1/10/23	== 2022.1.109.0.03 == 2020.2.125.3
CVE-2022-38492	High	January 10, 2023 1/10/23	== 2022.1.109.0.03 == 2020.2.125.3
CVE-2021-33231	Medium	October 20, 2022 10/20/22	== 2018.1.181.1

ivanti / service_manager

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2021-38560	Medium		February 1, 2022 2/1/22	== 2021.1

Showing vulnerabilities for 5 products matching "service_manager". 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.