Vulnerability Database

381,465

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 Exploit Date Affected versions
CVE-2016-0259
Low June 26, 2016 6/26/16
= 8.0.0.1
= 8.0.0.2
= 8.0.0.3
= 8.0.0.4
CVE-2015-7473
Low June 26, 2016 6/26/16
= 8.0.0.1
= 8.0.0.2
= 8.0.0.3
= 8.0.0.4
CVE-2015-7462
Low June 19, 2016 6/19/16
= 8.0.0.4
CVE-2015-2012
Low February 8, 2016 2/8/16
= 7.1.0.3
= 7.1.0.4
= 7.1.0.5
= 7.1.0.6
= 7.5
= 7.5.0.2
= 7.5.0.3
= 7.5.0.4
= 7.5.0.5
= 8.0
= 8.0.0.1
= 8.0.0.2
= 8.0.0.3
CVE-2015-2013
Medium September 14, 2015 9/14/15
= 7.0.1.0
= 7.0.1.1
= 7.0.1.2
= 7.0.1.3
= 7.0.1.4
= 7.0.1.5
= 7.0.1.6
= 7.0.1.7
= 7.0.1.8
= 7.0.1.9
= 7.0.1.10
= 7.0.1.11
= 7.0.1.12
CVE-2015-1967
Medium July 1, 2015 7/1/15
= 8.0.0.2
CVE-2015-0189
Medium May 20, 2015 5/20/15
= 7.5
= 7.5.0.1
= 7.5.0.2
= 7.5.0.3
= 7.5.0.4
= 8.0
= 8.0.0.1
CVE-2015-0176
Medium April 27, 2015 4/27/15
= 8.0
= 8.0.0.1
<= 7.5.0.4
CVE-2014-4771
Low February 13, 2015 2/13/15
= 7.0.1.0
= 7.0.1.1
= 7.0.1.2
= 7.0.1.3
= 7.0.1.4
= 7.0.1.5
= 7.0.1.6
= 7.0.1.7
= 7.0.1.8
= 7.0.1.9
= 7.0.1.10
= 7.0.1.11
= 7.0.1.12
= 7.1
= 7.1.0.1
= 7.1.0.2
= 7.1.0.3
= 7.1.0.4
= 7.1.0.5
= 7.5
= 7.5.0.1
= 7.5.0.2
= 7.5.0.3
= 7.5.0.4
= 8.0.0.0
CVE-2014-6116
Medium October 19, 2014 10/19/14
= 8.0.0.1
CVE-2014-4822
Low October 19, 2014 10/19/14
= 8.0.0.0
CVE-2014-4793
Medium October 2, 2014 10/2/14
= 8.0.0.0
CVE-2014-0911
Medium May 7, 2014 5/7/14
= 7.1
= 7.1.0.1
= 7.1.0.2
= 7.1.0.3
= 7.1.0.4
= 7.5
= 7.5.0.1
= 7.5.0.2
= 7.5.0.3
CVE-2013-4054
Medium March 2, 2014 3/2/14
= 7.5
= 7.5.0.1
= 7.5.0.2
CVE-2013-3028
Medium July 2, 2013 7/2/13
= 7.0
= 7.0.0.1
= 7.0.0.2
= 7.0.1.0
= 7.0.1.1
= 7.0.1.2
= 7.0.1.3
= 7.0.1.4
= 7.0.1.5
= 7.0.1.6
= 7.0.1.7
= 7.0.1.8
= 7.0.1.9
= 7.0.1.10
= 7.1
= 7.1.0.1
= 7.1.0.2
= 7.5
= 7.5.0.1
CVE-2012-2199
Medium September 25, 2012 9/25/12
= 7.0.1.0
= 7.0.1.1
= 7.0.1.2
= 7.0.1.3
= 7.0.1.4
= 7.0.1.5
= 7.0.1.6
= 7.0.1.7
= 7.0.1.8
= 7.1
= 7.5
CVE-2012-3295
Medium August 29, 2012 8/29/12
= 7.1
CVE-2012-2206
Low August 17, 2012 8/17/12
= 7.0
= 7.0.0.1
= 7.0.1.0
= 7.0.2.0
= 7.0.2.2
= 7.0.4
= 7.0.4.0
CVE-2012-3294
Medium August 17, 2012 8/17/12
<= 7.0.4
= 7.0
= 7.0.0.1
= 7.0.1.0
= 7.0.2.0
= 7.0.2.2
= 7.0.4.0
CVE-2011-1378
Low November 26, 2011 11/26/11
= 6.0
CVE-2009-0900
Medium October 30, 2011 10/30/11
= 6.0
= 6.0.1.0
= 6.0.1.1
= 6.0.2.0
= 6.0.2.1
= 6.0.2.2
= 6.0.2.3
= 6.0.2.4
= 6.0.2.5
= 6.0.2.6
= 6.0.2.10
= 7.0
= 7.0.0.1
= 7.0.0.2
CVE-2009-0905
Low October 30, 2011 10/30/11
= 6.0
= 6.0.1.0
= 6.0.1.1
= 6.0.2.0
= 6.0.2.1
= 6.0.2.2
= 6.0.2.3
= 6.0.2.4
= 6.0.2.5
= 6.0.2.6
= 6.0.2.7
= 7.0
= 7.0.0.1
= 7.0.0.2
CVE-2010-0780
Medium October 29, 2011 10/29/11
= 7.0
= 7.0.0.1
= 7.0.0.2
= 7.0.1.0
= 7.0.1.1
= 7.0.1.2
= 7.0.1.3
CVE-2011-1224
Medium July 7, 2011 7/7/11
= 6.0
= 6.0.1.0
= 6.0.1.1
= 6.0.2.0
= 6.0.2.1
= 6.0.2.2
= 6.0.2.3
= 6.0.2.4
= 6.0.2.5
= 6.0.2.6
= 6.0.2.7
= 6.0.2.8
= 6.0.2.9
= 6.0.2.10
= 7.0
= 7.0.0.1
= 7.0.0.2
= 7.0.1.0
= 7.0.1.1
= 7.0.1.2
= 7.0.1.3
= 7.0.1.4
CVE-2011-0310
Medium January 13, 2011 1/13/11
= 7.0
= 7.0.0.1
= 7.0.0.2
= 7.0.1.0
= 7.0.1.1
= 7.0.1.2
= 7.0.1.3
CVE-2011-0314
Medium January 12, 2011 1/12/11
= 6.0
= 6.0.1.0
= 6.0.1.1
= 6.0.2.0
= 6.0.2.1
= 6.0.2.2
= 6.0.2.3
= 6.0.2.4
= 6.0.2.5
= 6.0.2.6
= 6.0.2.7
= 6.0.2.8
= 6.0.2.9
= 6.0.2.10
= 7.0
= 7.0.0.1
= 7.0.0.2
= 7.0.1
= 7.0.1.0
= 7.0.1.1
= 7.0.1.2
= 7.0.1.3
= 7.0.1.4
CVE-2010-2638
Medium November 15, 2010 11/15/10
= 7.0
= 7.0.0.1
= 7.0.0.2
= 7.0.1.0
= 7.0.1.1
= 7.0.1.2
= 7.0.1.3
= 7.0.1.4
CVE-2010-2637
Medium November 12, 2010 11/12/10
= 6.0
= 6.0.0.0
= 6.0.1.0
= 6.0.1.1
= 6.0.2.0
= 6.0.2.1
= 6.0.2.2
= 6.0.2.3
= 6.0.2.4
= 6.0.2.5
= 6.0.2.6
= 6.0.2.7
= 6.0.2.8
= 6.0.2.10
= 7.0
= 7.0.0.1
= 7.0.0.2
= 7.0.1.0
CVE-2010-0782
Medium October 20, 2010 10/20/10
= 6.0
= 6.0.1.0
= 6.0.1.1
= 6.0.2.0
= 6.0.2.1
= 6.0.2.2
= 6.0.2.3
= 6.0.2.4
= 6.0.2.5
= 6.0.2.6
= 6.0.2.7
= 6.0.2.8
= 6.0.2.9
= 7.0
= 7.0.0.1
= 7.0.0.2
= 7.0.1.0
= 7.0.1.1
= 7.0.1.2
CVE-2010-0772
Medium April 27, 2010 4/27/10
= 7.0.0
= 7.0.1
= 7.0.1.1
CVE-2009-3159
High September 10, 2009 9/10/09
= 7.0.0.0
= 7.0.0.1
= 7.0.0.2
CVE-2009-3160
High September 10, 2009 9/10/09
= 6
= 6.0
= 6.0.0.0
= 6.0.1.0
= 6.0.1.1
= 6.0.2.0
= 6.0.2.1
= 6.0.2.2
= 6.0.2.3
= 6.0.2.4
= 6.0.2.5
= 6.0.2.6
= 6.0.2.7
= 7.0.0.0
= 7.0.0.1
= 7.0.0.2
= 7.0.1.0
CVE-2009-3161
High September 10, 2009 9/10/09
= 7.0.0.1
= 7.0.0.2
= 7.0.1.0
CVE-2009-0896
High June 3, 2009 6/3/09
= 6.0
= 6.0.0.0
= 6.0.1.0
= 6.0.1.1
= 6.0.2.0
= 6.0.2.1
= 6.0.2.2
= 6.0.2.3
= 6.0.2.4
= 6.0.2.5
= 6.0.2.6
= 7.0
= 7.0.0.1
= 7.0.0.2
CVE-2009-0439
High February 24, 2009 2/24/09
= 5.3
= 5.3.1
= 6.0.0.0
= 6.0.1.0
= 6.0.1.1
= 6.0.2.0
= 6.0.2.1
= 6.0.2.2
= 6.0.2.3
= 6.0.2.4
= 7.0
= 7.0.0.1
CVE-2008-1592
Medium March 31, 2008 3/31/08
= 5.1
= 5.3
= 5.3.1
CVE-2007-6705
Low March 9, 2008 3/9/08
<= 5.3
<= 6.0.2.0
CVE-2008-1130
Medium March 4, 2008 3/4/08
= 5.3
= 6
CVE-2007-6044
High November 20, 2007 11/20/07
= 6.0

Frequently Asked Questions

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.