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

Total vulnerabilities in the database

Vulnerabilities for products matching "imanager"

Found 3 matching products. Filters apply to all results.

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

novell / imanager

16 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2017-7430	Medium	May 3, 2017 5/3/17	`= 2.7` `= 2.7-sp1` `= 2.7-sp2` `= 2.7-sp3` `= 2.7-sp4` `= 2.7-sp4_patch1` `= 2.7-sp4_patch2` `= 2.7-sp4_patch3` `= 2.7-sp4_patch4` `= 2.7-sp5` `= 2.7-sp6` `= 2.7-sp7` `= 2.7-sp7_patch_1` `= 2.7-sp7_patch_10` `= 2.7-sp7_patch_2` `= 2.7-sp7_patch_3` `= 2.7-sp7_patch_4` `= 2.7-sp7_patch_5` `= 2.7-sp7_patch_6` `= 2.7-sp7_patch_7` `= 2.7-sp7_patch_8` `= 2.7-sp7_patch_9`
CVE-2017-7431	Medium	May 3, 2017 5/3/17	`= 2.7` `= 2.7-sp1` `= 2.7-sp2` `= 2.7-sp3` `= 2.7-sp4` `= 2.7-sp4_patch1` `= 2.7-sp4_patch2` `= 2.7-sp4_patch3` `= 2.7-sp4_patch4` `= 2.7-sp5` `= 2.7-sp6` `= 2.7-sp7` `= 2.7-sp7_patch_1` `= 2.7-sp7_patch_10` `= 2.7-sp7_patch_2` `= 2.7-sp7_patch_3` `= 2.7-sp7_patch_4` `= 2.7-sp7_patch_5` `= 2.7-sp7_patch_6` `= 2.7-sp7_patch_7` `= 2.7-sp7_patch_8` `= 2.7-sp7_patch_9`
CVE-2017-7432	High	May 3, 2017 5/3/17	`= 2.7` `= 2.7-sp1` `= 2.7-sp2` `= 2.7-sp3` `= 2.7-sp4` `= 2.7-sp4_patch1` `= 2.7-sp4_patch2` `= 2.7-sp4_patch3` `= 2.7-sp4_patch4` `= 2.7-sp5` `= 2.7-sp6` `= 2.7-sp7` `= 2.7-sp7_patch_1` `= 2.7-sp7_patch_10` `= 2.7-sp7_patch_2` `= 2.7-sp7_patch_3` `= 2.7-sp7_patch_4` `= 2.7-sp7_patch_5` `= 2.7-sp7_patch_6` `= 2.7-sp7_patch_7` `= 2.7-sp7_patch_8` `= 2.7-sp7_patch_9`
CVE-2017-5186	Medium	April 27, 2017 4/27/17	`<= 2.7`
CVE-2013-1088	Medium	April 24, 2013 4/24/13	`<= 2.7` `= 2.7` `= 2.7-refresh6` `= 2.7-sp4` `= 2.7-sp4_patch1` `= 2.7-sp4_patch2` `= 2.7-sp4_patch3` `= 2.7-sp4_patch4` `= 2.7-sp5` `= 2.7.1` `= 2.7.2` `= 2.7.3` `= 2.7.3-ftf2` `= 2.7.3-ftf4` `= 2.7.3-sp3` `= 2.7.4` `= 2.7.5`
CVE-2013-3268	High	April 24, 2013 4/24/13	`<= 2.7` `= 2.7-refresh6` `= 2.7-sp4` `= 2.7-sp4_patch1` `= 2.7-sp4_patch2` `= 2.7-sp4_patch3` `= 2.7-sp4_patch4` `= 2.7-sp5` `= 2.7.0` `= 2.7.1` `= 2.7.2` `= 2.7.3` `= 2.7.3-ftf2` `= 2.7.3-ftf4` `= 2.7.3-sp3` `= 2.7.4` `= 2.7.5`
CVE-2011-4188	Medium	April 9, 2012 4/9/12	`<= 2.7.4` `= 1.5` `= 2.0` `= 2.0.2` `= 2.5` `= 2.6.0` `= 2.7.0` `= 2.7.3` `= 2.7.3-ftf4` `= 2.7.3-sp3`
CVE-2010-1929	High	June 28, 2010 6/28/10	`= 2.7.0` `= 2.7.3` `= 2.7.3-ftf2`
CVE-2010-1930	Medium	June 28, 2010 6/28/10	`= 2.7.0` `= 2.7.3` `= 2.7.3-ftf2`
CVE-2009-4486	High	January 8, 2010 1/8/10	`<= 2.7.2` `= 1.5` `= 2.0` `= 2.0.2` `= 2.5` `= 2.6.0` `= 2.7.1`
CVE-2008-3488	High	August 6, 2008 8/6/08	`= 1.5` `= 2.0` `= 2.0.2` `= 2.5` `= 2.5-ir3` `= 2.6.0` `= 2.7.0`
CVE-2006-4517	High	November 1, 2006 11/1/06	`<= 2.5` `= 1.5` `= 2.0` `= 2.0.2`
CVE-2005-1730	High	December 31, 2005 12/31/05	`<= 2.0.2`
CVE-2004-0079	High	November 23, 2004 11/23/04	`= 1.5` `= 2.0`
CVE-2004-0081	Medium	November 23, 2004 11/23/04	`= 1.5` `= 2.0`
CVE-2004-0112	Medium	November 23, 2004 11/23/04	`= 1.5` `= 2.0`

netiq / imanager

12 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2022-38758	High	January 26, 2023 1/26/23	`< 3.2.6`
CVE-2018-12462	Medium	July 10, 2018 7/10/18	`= 3.1.1`
CVE-2018-1344	Low	March 21, 2018 3/21/18	`< 3.1`
CVE-2018-1345	Medium	March 21, 2018 3/21/18	`< 3.1`
CVE-2018-1347	Medium	March 21, 2018 3/21/18	`< 3.1`
CVE-2017-5189	Medium	March 2, 2018 3/2/18	`= 2.7` `= 2.7.1` `= 2.7.2` `= 2.7.3` `= 2.7.4` `= 2.7.5` `= 2.7.6` `= 2.7.7-p10` `= 2.7.7-p11` `= 2.7.7-p4` `= 2.7.7-p5` `= 2.7.7-p6` `= 2.7.7-p7` `= 2.7.7-p8` `= 2.7.7-p9` `= 2.7.7.10-hf1` `= 2.7.7.10-hf2` `= 3.0` `= 3.0-sp1` `= 3.0-sp2` `= 3.0-sp3` `= 3.0-sp4` `= 3.0.2-p1` `= 3.0.3`
CVE-2017-7425	High	November 6, 2017 11/6/17	`<= 2.7.7` `= 3.0.3.2`
CVE-2017-7428	Medium	May 3, 2017 5/3/17	`= 3.0` `= 3.0.1` `= 3.0.2` `= 3.0.2.1` `= 3.0.3` `= 3.0.3.1`
CVE-2017-7430	Medium	May 3, 2017 5/3/17	`= 3.0` `= 3.0.1` `= 3.0.2` `= 3.0.2.1` `= 3.0.3` `= 3.0.3.1`
CVE-2017-7431	Medium	May 3, 2017 5/3/17	`= 3.0` `= 3.0.1` `= 3.0.2` `= 3.0.2.1` `= 3.0.3` `= 3.0.3.1`
CVE-2017-7432	High	May 3, 2017 5/3/17	`= 3.0` `= 3.0.1` `= 3.0.2` `= 3.0.2.1` `= 3.0.3` `= 3.0.3.1`
CVE-2017-5186	Medium	April 27, 2017 4/27/17	`= 3.0` `= 3.0.1` `= 3.0.2`

microfocus / imanager

22 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2021-38119	Medium	November 22, 2024 11/22/24	`>= 3.0, < 3.2.5`
CVE-2021-38134	Medium	November 22, 2024 11/22/24	`>= 3.0, < 3.2.6`
CVE-2021-38135	High	November 22, 2024 11/22/24	`>= 3.0, <= 3.2.5` `= 3.2.6`
CVE-2022-26324	High	November 22, 2024 11/22/24	`= 3.2.6`
CVE-2023-24466	High	November 22, 2024 11/22/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2`
CVE-2023-24467	High	November 22, 2024 11/22/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2`
CVE-2021-38116	High	November 22, 2024 11/22/24	`< 3.2.5`
CVE-2021-38117	High	November 22, 2024 11/22/24	`>= 3.0, < 3.2.5`
CVE-2021-38118	Medium	November 22, 2024 11/22/24	`>= 3.0, < 3.2.5`
CVE-2020-11859	High	November 6, 2024 11/6/24	`< 3.2.3`
CVE-2024-4429	Medium	May 28, 2024 5/28/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3` `= 3.2.6-patch3_hotfix1`
CVE-2024-3969	High	May 28, 2024 5/28/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3`
CVE-2024-3970	Medium	May 15, 2024 5/15/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3`
CVE-2024-3968	High	May 15, 2024 5/15/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3`
CVE-2024-3967	High	May 15, 2024 5/15/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3`
CVE-2024-3488	Medium	May 15, 2024 5/15/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3`
CVE-2024-3487	Low	May 15, 2024 5/15/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3`
CVE-2024-3486	High	May 15, 2024 5/15/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3`
CVE-2024-3485	Medium	May 15, 2024 5/15/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3`
CVE-2024-3484	Medium	May 15, 2024 5/15/24	`>= 3.0, < 3.2.6` `= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3`
CVE-2024-3483	High	May 15, 2024 5/15/24	`>= 3.0, <= 3.2.6` `= 3.2.6-patch1` `= 3.2.6-patch2` `= 3.2.6-patch3`
CVE-2018-17949	Medium	December 12, 2018 12/12/18	`< 3.1.2`

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