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

Found 1 matching product.

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

ibm / qradar_security_information_and_event_manager

185 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2018-2024	High	July 22, 2019 7/22/19	== 7.2.0 == 7.3.0
CVE-2019-4211	Medium	July 17, 2019 7/17/19	>= 7.3.0 <= 7.3.2 >= 7.2.0 <= 7.2.8.15
CVE-2018-2021	Medium	July 17, 2019 7/17/19	>= 7.2.0 < 7.2.8 >= 7.3.0 <= 7.3.2 == 7.2.8-p14 == 7.2.8-p15 == 7.2.8-p2 == 7.2.8-p1 == 7.2.8-p5 == 7.2.8-p6 == 7.2.8-p3 == 7.2.8-p4 == 7.2.8-p7 == 7.2.8-p8 == 7.2.8-p9 == 7.2.8-p10 == 7.2.8-p11 == 7.2.8-p12 == 7.2.8-p13 == 7.2.8
CVE-2018-2022	Medium	July 17, 2019 7/17/19	== 7.2.8-p2 == 7.2.8-p1 == 7.2.8-p5 == 7.2.8-p6 == 7.2.8-p3 == 7.2.8-p4 >= 7.2.0 < 7.2.8 == 7.2.8-p7 == 7.2.8-p8 == 7.2.8-p9 == 7.2.8-p10 == 7.2.8-p11 == 7.2.8-p12 == 7.2.8-p13 == 7.2.8 >= 7.3.0 <= 7.3.2 == 7.2.8-p14 == 7.2.8-p15
CVE-2019-4054	Low	July 17, 2019 7/17/19	>= 7.3.0 <= 7.3.2 >= 7.2.0 <= 7.2.8.15
CVE-2019-4264	Medium	May 29, 2019 5/29/19	== 7.2.8-p2 == 7.2.8-p1 == 7.2.8 >= 7.1.2 < 7.2.8
CVE-2018-1729	Medium	April 19, 2019 4/19/19	>= 7.3.0 <= 7.3.2
CVE-2019-4210	High	April 8, 2019 4/8/19	== 7.3.2 == 7.3.2-if01
CVE-2017-1695	Medium	February 15, 2019 2/15/19	== 7.2.8-p2 == 7.2.8-p1 == 7.2.8-p5 == 7.2.8-p6 == 7.2.8-p3 == 7.2.8-p4 == 7.3.1-p1 == 7.3.1-p2 == 7.2.8-p7 == 7.2.8-p8 == 7.2.8-p9 == 7.2.8-p10 == 7.2.8-p11 >= 7.2.0 <= 7.2.8 == 7.3.1-p4 == 7.3.1-p3 >= 7.3.0 <= 7.3.1 == 7.2.8 == 7.3.1
CVE-2018-1733	Medium	January 29, 2019 1/29/19	>= 7.2.0 <= 7.2.8 == 7.2.8-p13 >= 7.3.0 <= 7.3.1 == 7.3.1-p6
CVE-2018-1730	Medium	December 5, 2018 12/5/18	>= 7.2.0 <= 7.2.8 == 7.2.8-p13 >= 7.3.0 <= 7.3.1 == 7.3.1-p6
CVE-2018-1571	High	September 11, 2018 9/11/18	== 7.2.8-p2 == 7.2.8 == 7.2.8-p1 == 7.2.8-p5 == 7.2.8-p6 == 7.2.8-p3 == 7.3.0 == 7.2.8-p4 == 7.3.1 == 7.3.1-p1 == 7.3.1-p2 == 7.2.8-p7 == 7.2.8-p8 == 7.2.8-p9 == 7.2.8-p10 == 7.2.8-p11 == 7.3.1-p4 == 7.3.1-p3 == 7.2.8-p12 == 7.2.8-p13 >= 7.2.0 <= 7.2.7
CVE-2018-1612	Medium	July 17, 2018 7/17/18	== 7.2.8-p2 == 7.2.8-p1 == 7.2.8-p5 == 7.2.8-p6 == 7.2.8-p3 == 7.2.8-p4 == 7.2.8-p7 == 7.2.8-p8 == 7.2.8-p9 == 7.2.8-p10 == 7.2.8-p11 >= 7.2.0 <= 7.2.8 == 7.3.0 == 7.3.1 == 7.3.1-p1 == 7.3.1-p2 == 7.3.1-p4 == 7.3.1-p3
CVE-2017-1721	Medium	April 26, 2018 4/26/18	== 7.2.8-p2 == 7.3.0-p1 == 7.2.8 == 7.2.8-p1 == 7.2.8-p5 == 7.2.8-p6 == 7.2.8-p3 == 7.3.0 == 7.2.8-p4 >= 7.2.0 < 7.2.8 == 7.2.8-p7 == 7.2.8-p8 == 7.2.8-p9 == 7.2.8-p10 == 7.2.8-p11 == 7.3.0-p2 == 7.3.0-p3 == 7.3.0-p4 == 7.3.0-p5 == 7.3.0-p6 == 7.3.0-p7
CVE-2017-1722	Medium	April 26, 2018 4/26/18	== 7.2.8-p2 == 7.3.0-p1 == 7.2.8 == 7.2.8-p1 == 7.2.8-p5 == 7.2.8-p6 == 7.2.8-p3 == 7.3.0 == 7.2.8-p4 >= 7.2.0 < 7.2.8 == 7.2.8-p7 == 7.2.8-p8 == 7.2.8-p9 == 7.2.8-p10 == 7.2.8-p11 == 7.3.0-p2 == 7.3.0-p3 == 7.3.0-p4 == 7.3.0-p5 == 7.3.0-p6 == 7.3.0-p7
CVE-2017-1723	Low	April 26, 2018 4/26/18	== 7.2.8-p2 == 7.2.8 == 7.2.8-p1 == 7.2.8-p5 == 7.2.8-p6 == 7.2.8-p3 == 7.3.0 == 7.2.8-p4 == 7.3.1 == 7.3.1-p1 == 7.3.1-p2 >= 7.2.0 < 7.2.8 == 7.2.8-p7 == 7.2.8-p8 == 7.2.8-p9 == 7.2.8-p10 == 7.2.8-p11
CVE-2017-1724	Low	April 26, 2018 4/26/18	== 7.2.8-p2 == 7.2.8 == 7.2.8-p1 == 7.2.8-p5 == 7.2.8-p6 == 7.2.8-p3 == 7.3.0 == 7.2.8-p4 == 7.3.1 == 7.3.1-p1 == 7.3.1-p2 >= 7.2.0 < 7.2.8 == 7.2.8-p7 == 7.2.8-p8 == 7.2.8-p9 == 7.2.8-p10 == 7.2.8-p11
CVE-2018-1418	Medium	April 26, 2018 4/26/18	== 7.2.8-p2 == 7.2.8-p1 == 7.2.8-p5 == 7.2.8-p6 == 7.2.8-p3 == 7.3.0 == 7.2.8-p4 == 7.3.1-p1 == 7.3.1-p2 >= 7.2.0 < 7.2.8 == 7.2.8-p7 == 7.2.8-p8 == 7.2.8-p9 == 7.2.8-p10 == 7.2.8-p11 == 7.2.8 == 7.3.1
CVE-2017-1624	Medium	April 4, 2018 4/4/18	== 7.3.0 == 7.3.1 == 7.3.1-p1 == 7.3.1-p2
CVE-2017-1733	Low	April 4, 2018 4/4/18	== 7.3.0 == 7.3.1 == 7.3.1-p1 == 7.3.1-p2
CVE-2015-2009	Medium	March 29, 2018 3/29/18	== 7.1.0 == 7.2.5-patch1 == 7.2.5-patch2 == 7.2.5-patch3 >= 7.2.0 < 7.2.5 == 7.1.0-mr1 == 7.1.0-mr2
CVE-2017-1623	Low	January 10, 2018 1/10/18	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.3.0 == 7.2.3
CVE-2016-9722	Low	January 10, 2018 1/10/18	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.3.0 == 7.2.3
CVE-2017-1696	High	December 20, 2017 12/20/17	== 7.3.0 == 7.3.0-patch1 == 7.3.0-patch2 == 7.3.0-patch3 == 7.3.0-patch4 == 7.3.0-patch5
CVE-2017-1162	Medium	September 12, 2017 9/12/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.3.0 == 7.2.3
CVE-2016-9738	Medium	June 27, 2017 6/27/17	== 7.2.8-p2 == 7.3.0-p1 == 7.2.8 == 7.2.7 == 7.2.0 == 7.2.8-p1 == 7.2.4 == 7.2.8-p5 == 7.2.6 == 7.2.1 == 7.2.8-p6 == 7.2.5 == 7.2.8-p3 == 7.2.2 == 7.3.0 == 7.2.3 == 7.2.8-p4
CVE-2016-9972	Low	June 27, 2017 6/27/17	== 7.2.8-p2 == 7.3.0-p1 == 7.2.8 == 7.2.7 == 7.2.0 == 7.2.8-p1 == 7.2.4 == 7.2.8-p5 == 7.2.6 == 7.2.1 == 7.2.8-p6 == 7.2.5 == 7.2.8-p3 == 7.2.2 == 7.3.0 == 7.2.3 == 7.2.8-p4
CVE-2017-1234	Low	June 27, 2017 6/27/17	== 7.2.8-p2 == 7.3.0-p1 == 7.2.8 == 7.2.7 == 7.2.0 == 7.2.8-p1 == 7.2.4 == 7.2.8-p5 == 7.2.6 == 7.2.1 == 7.2.8-p6 == 7.2.5 == 7.2.8-p3 == 7.2.2 == 7.3.0 == 7.2.3 == 7.2.8-p4
CVE-2016-9750	Low	May 15, 2017 5/15/17	== 7.2.0 == 7.3.0
CVE-2016-9720	Medium	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-9723	Low	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-9724	High	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-9725	Medium	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-9726	High	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-9727	High	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-9728	Medium	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-9729	Medium	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-9730	Low	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-9740	High	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2017-1133	Low	March 7, 2017 3/7/17	== 7.2.8 == 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-2879	Low	March 1, 2017 3/1/17	== 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-2880	Low	March 1, 2017 3/1/17	== 7.2.7 == 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3
CVE-2016-2881	Medium	November 30, 2016 11/30/16	== 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 <= 7.1.0 == 7.2.2 == 7.2.3
CVE-2016-2878	Medium	November 30, 2016 11/30/16	== 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 == 7.2.2 == 7.2.3 == 7.1.0
CVE-2016-2877	Low	November 30, 2016 11/30/16	== 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 <= 7.1.0 == 7.2.2 == 7.2.3
CVE-2016-2876	High	November 30, 2016 11/30/16	== 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 <= 7.1.0 == 7.2.2 == 7.2.3
CVE-2016-2874	Low	November 30, 2016 11/30/16	== 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 <= 7.1.0 == 7.2.2 == 7.2.3
CVE-2016-2873	Medium	November 30, 2016 11/30/16	== 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 <= 7.1.0 == 7.2.2 == 7.2.3
CVE-2016-2871	Low	November 30, 2016 11/30/16	== 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 <= 7.1.0 == 7.2.2 == 7.2.3
CVE-2016-2869	Low	November 30, 2016 11/30/16	== 7.2.0 == 7.2.4 == 7.2.6 == 7.2.1 == 7.2.5 <= 7.1.0 == 7.2.2 == 7.2.3

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.