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.

326,214

Total vulnerabilities in the database

Vulnerabilities for products matching "websphere_mq"

Found 1 matching product.

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

ibm / websphere_mq

89 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2012-2201	High	September 29, 2022 9/29/22	== 7.1
CVE-2021-38949	Medium	November 16, 2021 11/16/21	== 7.5
CVE-2020-4682	Critical	January 28, 2021 1/28/21	== 7.5.0.1 == 7.5.0.2 == 7.5.0.3 == 7.5.0.5 == 7.5.0.6 == 7.5.0.4 == 7.5.0.7 == 7.5.0.8 == 7.5.0.9 == 7.5.0.0
CVE-2020-4310	High	June 16, 2020 6/16/20	== 7.1 == 7.5
CVE-2019-4619	Medium	March 16, 2020 3/16/20	>= 7.1.0.0 <= 7.5.0.9
CVE-2019-4656	Medium	March 16, 2020 3/16/20	>= 7.1.0.0 <= 7.5.0.9
CVE-2019-4719	Medium	March 16, 2020 3/16/20	>= 7.1.0.0 <= 7.5.0.9
CVE-2012-4863	Medium	January 23, 2020 1/23/20	>= 7.1.0.0 < 7.1.0.2 >= 7.5.0.0 < 7.5.0.1
CVE-2019-4141	Medium	September 27, 2019 9/27/19	>= 9.0.0.0 <= 9.0.0.6 >= 7.1.0.0 <= 7.1.0.9 >= 7.5.0.0 <= 7.5.0.9 >= 8.0.0.0 <= 8.0.0.11 >= 9.1.0.0 <= 9.1.0.2 >= 9.1.1 <= 9.1.2
CVE-2019-4261	Medium	August 5, 2019 8/5/19	>= 7.1.0.0 <= 7.1.0.9 >= 7.5 <= 7.5.0.9
CVE-2019-4039	Medium	May 23, 2019 5/23/19	>= 9.0.0.0 <= 9.0.0.5 >= 9.1.0 <= 9.1.1 >= 9.1.0.0 <= 9.1.0.1 >= 8.0.0.0 <= 8.0.0.11
CVE-2019-4078	High	May 23, 2019 5/23/19	>= 9.0.0.0 <= 9.0.0.5 == 9.1.1 >= 9.1.0.0 <= 9.1.0.1 >= 8.0.0.0 <= 8.0.0.11
CVE-2018-1925	Low	April 15, 2019 4/15/19	>= 9.1.0.0 <= 9.1.0.1 == 9.1.1
CVE-2018-1974	Medium	March 11, 2019 3/11/19	>= 9.0.0.0 <= 9.0.0.5 >= 8.0.0.0 <= 8.0.0.10 >= 9.1.0.0 <= 9.1.1
CVE-2018-1998	High	March 11, 2019 3/11/19	>= 9.0.0.0 <= 9.0.0.5 >= 8.0.0.0 <= 8.0.0.10 >= 9.1.0.0 <= 9.1.0.1
CVE-2018-1792	High	November 13, 2018 11/13/18	== 9.1.0.0 >= 9.0.1 <= 9.0.5 >= 9.0.0.0 <= 9.0.0.5 >= 8.0.0.0 <= 8.0.0.10
CVE-2018-1684	Low	November 9, 2018 11/9/18	== 9.1.0.0 >= 9.0.1 <= 9.0.5 >= 9.0.0.0 <= 9.0.0.5 >= 8.0.0.0 <= 8.0.0.10
CVE-2018-1551	Medium	August 6, 2018 8/6/18	>= 9.0.0.0 <= 9.0.0.3 >= 8.0.0.2 <= 8.0.0.8
CVE-2018-1503	Low	July 23, 2018 7/23/18	>= 9.0.0.0 <= 9.0.0.3 >= 8.0.0.0 <= 8.0.0.9 >= 7.5.0.0 <= 7.5.0.8
CVE-2018-1543	Low	June 27, 2018 6/27/18	== 8.0 == 9.0
CVE-2018-1374	Low	June 26, 2018 6/26/18	== 7.1.0.1 == 7.5.0.1 == 8.0.0.3 == 7.1.0.3 == 9.0.1 == 8.0.0.6 == 9.0.2 == 8.0.0.5 == 7.1 == 7.1.0.4 == 8.0.0.0 == 7.1.0.2 == 7.1.0.5 == 7.5.0.2 == 7.1.0.6 == 7.5.0.3 == 8.0.0.2 == 7.5 == 9.0.0.0 == 7.5.0.4 == 8.0.0.4 == 8.0.0.1 == 9.0.0.1 == 8.0.0.7 == 9.0.3 == 9.0.4 == 7.1.0.7 == 7.1.0.8 == 9.0.0.2 == 8.0.0.8 == 9.0.0 == 7.1.0.9
CVE-2018-1419	Low	June 15, 2018 6/15/18	== 8.0.0.3 == 9.0.1 == 8.0.0.6 == 9.0.2 == 8.0.0.5 == 8.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1 == 9.0 == 9.0.0.1 == 8.0.0.7 == 9.0.3 == 9.0.4 == 9.0.0.2 == 8.0.0.8
CVE-2017-1786	Low	April 23, 2018 4/23/18	>= 8.0 <= 8.0.0.8 >= 9.0 <= 9.0.4
CVE-2018-1371	Low	April 17, 2018 4/17/18	== 9.0.4 == 9.0.0.2 == 8.0.0.8
CVE-2015-1957	Low	April 10, 2018 4/10/18	>= 8.0 < 8.0.0.3 >= 7.5 < 7.5.0.6
CVE-2017-1747	Low	March 30, 2018 3/30/18	== 9.0.1 == 9.0.2 == 9.0 == 9.0.0.1 == 9.0.3 == 9.0.4 == 9.0.0.2
CVE-2018-1388	Medium	February 7, 2018 2/7/18	== 7.0.1.2 == 7.0.1.3 == 7.0.1.4 == 7.0.1.9 == 7.0.1.5 == 7.0.1.12 == 7.0.1.8 == 7.0.1.6 == 7.0.1.11 == 7.0.1.1 == 7.0.1.10 == 7.0.1.7 == 7.0.1.0 == 7.0.1.13 == 7.0.1.14
CVE-2017-1612	Low	January 9, 2018 1/9/18	== 7.5.0.1 == 7.5.0.2 == 7.5.0.3 == 7.5.0.5 == 7.5.0.6 == 7.5 == 7.5.0.4 == 7.5.0.7 == 7.5.0.8 == 7.0.1.2 == 7.0.1.3 == 7.0.1.4 == 7.0.1.9 == 7.0.1.5 == 7.0.1.12 == 7.0.1.8 == 7.0.1.6 == 7.0.1.11 == 7.0.1.1 == 7.0.1.10 == 7.0.1.7 == 7.0.1.0 == 7.0.1.13 == 7.0.1.14 == 7.1.0.1 == 7.1.0.3 == 7.1.0.4 == 7.1.0.2 == 7.1.0.5 == 7.1.0.6 == 7.1.0.7 == 7.1.0.8 == 7.1.0.0 == 8.0.0.3 == 8.0.0.6 == 8.0.0.5 == 8.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1 == 8.0.0.7 == 9.0 == 9.0.0.1 == 9.0.2.0 == 9.0.3.0 == 9.0.1.0
CVE-2017-1699	Low	January 4, 2018 1/4/18	== 8.0.0.3 == 9.0.1 == 8.0.0.6 == 9.0.2 == 8.0.0.5 == 8.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1 == 9.0 == 9.0.0.1 == 9.0.3
CVE-2017-1557	Low	January 2, 2018 1/2/18	== 8.0.0.3 == 9.0.1 == 8.0.0.6 == 9.0.2 == 8.0.0.5 == 8.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1 == 9.0 == 9.0.0.1 == 8.0.0.7 == 9.0.3
CVE-2017-1760	Low	December 11, 2017 12/11/17	== 7.5.0.1 == 8.0.0.3 == 9.0.1 == 8.0.0.6 == 9.0.2 == 8.0.0.5 == 8.0 == 7.5.0.2 == 7.5.0.3 == 7.5.0.5 == 8.0.0.2 == 7.5.0.6 == 7.5 == 7.5.0.4 == 8.0.0.4 == 8.0.0.1 == 9.0 == 9.0.0.1 == 9.0.3 == 7.5.0.7 == 7.5.0.8
CVE-2017-1341	Low	December 7, 2017 12/7/17	== 8.0.0.3 == 9.0.1 == 8.0.0.6 == 9.0.2 == 8.0.0.5 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1 == 9.0 == 9.0.0.1 == 8.0.0.7 == 9.0.3
CVE-2017-1433	Low	December 7, 2017 12/7/17	== 7.5.0.1 == 8.0.0.3 == 8.0.0.6 == 8.0.0.5 == 8.0 == 7.5.0.2 == 7.5.0.3 == 7.5.0.5 == 8.0.0.2 == 7.5.0.6 == 7.5 == 7.5.0.4 == 8.0.0.4 == 8.0.0.1 == 9.0 == 9.0.0.1 == 8.0.0.7 == 7.5.0.7 == 7.5.0.8
CVE-2017-1283	Low	November 27, 2017 11/27/17	== 8.0.0.3 == 9.0.1 == 8.0.0.6 == 9.0.2 == 8.0.0.5 == 8.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1 == 9.0 == 9.0.0.1 == 8.0.0.7 == 9.0.3 == 9.0.4
CVE-2017-1235	Low	September 25, 2017 9/25/17	== 8.0.0.3 == 8.0.0.6 == 8.0.0.5 == 8.0.0.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1
CVE-2017-1285	Low	July 12, 2017 7/12/17	== 9.0.1 == 9.0.2
CVE-2017-1284	Low	July 10, 2017 7/10/17	== 9.0.1 == 9.0.2
CVE-2017-1337	Low	July 10, 2017 7/10/17	== 9.0.1 == 9.0.2
CVE-2017-1236	Low	July 6, 2017 7/6/17	== 9.0.2
CVE-2017-1117	Low	June 21, 2017 6/21/17	== 8.0.0.3 == 9.0.1 == 8.0.0.5 == 8.0.0.0 == 8.0 == 8.0.0.2 == 9.0.0.0 == 8.0.0.4 == 8.0.0.1
CVE-2016-6089	Low	June 7, 2017 6/7/17	== 9.0.1 == 9.0.0.0
CVE-2017-1145	High	March 20, 2017 3/20/17	== 8.0.0.6
CVE-2016-8971	Medium	March 7, 2017 3/7/17	== 8.0.0.3 == 8.0.0.5 == 8.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1
CVE-2016-9009	Low	February 24, 2017 2/24/17	== 8.0.0.3 == 8.0.0.5 == 8.0.0.0 == 8.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1
CVE-2016-3013	Low	February 22, 2017 2/22/17	<= 8.0.0.5
CVE-2016-3052	Low	February 22, 2017 2/22/17	<= 8.0.0.5
CVE-2016-8915	Low	February 22, 2017 2/22/17	== 8.0.0.3 == 8.0.0.5 == 8.0.0.0 == 8.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1
CVE-2016-8986	Low	February 22, 2017 2/22/17	== 8.0.0.3 == 8.0.0.5 == 8.0.0.0 == 8.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1
CVE-2016-0379	Low	September 26, 2016 9/26/16	== 7.5.0.1 == 8.0.0.3 == 8.0 == 7.5.0.2 == 7.5.0.3 == 7.5.0.5 == 8.0.0.2 == 7.5.0.6 == 7.5 == 7.5.0.4 == 8.0.0.4 == 8.0.0.1
CVE-2016-0260	Medium	June 29, 2016 6/29/16	== 8.0.0.3 == 8.0 == 8.0.0.2 == 8.0.0.4 == 8.0.0.1

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.