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

Total vulnerabilities in the database

Vulnerabilities for products matching "business_process_manager"

Found 1 matching product.

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

ibm / business_process_manager

88 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2016-9693	Medium	March 7, 2017 3/7/17	== 7.5.0.0 == 7.5.0.1 == 7.5.1.0 == 7.5.1.1 == 7.5.1.2 == 8.0.0.0 == 8.0.1.0 == 8.0.1.1 == 8.0.1.2 == 8.0.1.3 == 8.5.0.0 == 8.5.0.1 == 8.5.0.2 == 8.5.5.0 == 8.5.6.0 == 8.5.6.2 == 8.5.7.0
CVE-2016-9731	Low	February 1, 2017 2/1/17	== 8.5.7.0
CVE-2016-3056	Low	October 14, 2016 10/14/16	== 8.5.5.0 == 7.5.0.0 == 8.5.6.2 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 8.5.0.2 == 7.5.1.0 == 8.0.0.0 == 8.5.0.0 == 7.5.1.1 == 8.5.7.0 == 7.5.0.1 == 8.5.6.0 == 8.0.1.0 == 7.5.1.2 == 8.0.1.1
CVE-2016-5901	Low	October 5, 2016 10/5/16	== 8.5.6.2 == 8.5.6.1 == 8.5.7.0 == 8.5.6.0
CVE-2016-0349	Low	June 30, 2016 6/30/16	== 8.5.7.0 == 8.5.6.0
CVE-2015-7454	Low	March 21, 2016 3/21/16	== 7.5.0.0 == 7.5.0.1 == 7.5.1.0 == 7.5.1.1 == 7.5.1.2 == 8.0.0.0 == 8.0.1.0 == 8.0.1.1 == 8.0.1.2 == 8.0.1.3 == 8.5.0.0 == 8.5.0.1 == 8.5.0.2 == 8.5.5.0 == 8.5.6.0 == 8.5.6.1 == 8.5.6.2
CVE-2016-0227	Low	March 3, 2016 3/3/16	== 8.5.5.0 == 8.5.6.2 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 8.5.0.2 == 8.0.0.0 == 8.5.0.0 == 8.0.1.0 == 8.5.6.0 == 8.0.1.1
CVE-2015-8524	Low	February 29, 2016 2/29/16	== 8.5.5.0 == 8.5.6.2 == 8.5.0.1 == 8.5.0.2 == 8.5.0.0 == 8.5.6.0
CVE-2015-7441	Low	January 1, 2016 1/1/16	== 8.5.5.0 == 8.5.6.1 == 7.5.0.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 7.5.1.0 == 8.0.0.0 == 8.5.0.0 == 7.5.1.1 == 8.5.6.2 == 7.5.0.1 == 8.5.6.0 == 8.0.1.0 == 7.5.1.2 == 8.0.1.1
CVE-2015-4955	Low	October 3, 2015 10/3/15	== 8.5.5.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 8.0.0.0 == 8.5.0.0 == 8.5.6.0 == 8.0.1.0 == 8.0.1.1
CVE-2015-1904	Low	August 1, 2015 8/1/15	== 8.5.5.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 8.0.0.0 == 8.5.0.0 == 8.0.1.0 == 8.5.6.0 == 8.0.1.1
CVE-2015-1905	Low	July 21, 2015 7/21/15	== 7.5.0.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 7.5.1.0 == 8.0.0.0 == 8.5.0.0 == 7.5.1.1 == 7.5.0.1 == 8.5.6.0 == 8.0.1.0 == 7.5.1.2 == 8.0.1.1
CVE-2015-1906	Low	July 21, 2015 7/21/15	== 8.5.5.0 == 7.5.0.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 7.5.1.0 == 8.0.0.0 == 8.5.0.0 == 7.5.1.1 == 7.5.0.1 == 8.5.6.0 == 8.0.1.0 == 7.5.1.2 == 8.0.1.1
CVE-2015-1961	High	July 13, 2015 7/13/15	== 8.5.5.0 == 7.5.0.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 7.5.1.0 == 8.0.0.0 == 7.5.1.1 == 7.5.0.1 == 8.5.0.0 == 8.0.1.0 == 8.5.6.0 == 8.0.1.1
CVE-2015-1884	Low	June 28, 2015 6/28/15	== 8.5.5.0 == 7.5.0.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 7.5.1.0 == 8.0.0.0 == 8.5.0.0 == 7.5.1.1 == 7.5.0.1 == 8.0.1.0 == 7.5.1.2 == 8.0.1.1
CVE-2015-0193	Low	May 30, 2015 5/30/15	== 8.5.5.0 == 7.5.0.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 7.5.1.0 == 8.0.0.0 == 8.5.0.0 == 7.5.1.1 == 7.5.0.1 == 8.0.1.0 == 7.5.1.2 == 8.0.1.1
CVE-2015-0156	Low	May 25, 2015 5/25/15	== 8.5.5.0 == 7.5.0.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 7.5.1.0 == 8.0.0.0 == 8.5.0.0 == 7.5.1.1 == 7.5.0.1 == 8.5.6.0 == 8.0.1.0 == 7.5.1.2 == 8.0.1.1
CVE-2015-0158	Low	March 24, 2015 3/24/15	== 8.5.5.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 8.0.0.0 == 8.5.0.0 == 8.0.1.0 == 8.0.1.1
CVE-2015-0106	Low	March 24, 2015 3/24/15	== 8.5.5.0 == 7.5.0.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 7.5.1.0 == 8.0.0.0 == 7.5.1.1 == 7.5.0.1 == 8.5.0.0 == 8.0.1.0 == 7.5.1.2 == 8.0.1.1
CVE-2015-0105	Low	March 24, 2015 3/24/15	== 8.5.5.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 8.0.0.0 == 8.5.0.0 == 8.0.1.0 == 8.0.1.1
CVE-2015-0103	Low	March 24, 2015 3/24/15	== 8.5.5.0 == 8.5.0.1 == 8.0.1.2 == 8.0.1.3 == 8.0.0.0 == 8.5.0.0 == 8.0.1.0 == 8.0.1.1
CVE-2014-6139	Low	February 13, 2015 2/13/15	== 8.5.5.0 == 8.0.1.3 == 8.5.0.1
CVE-2014-8914	Low	January 21, 2015 1/21/15	== 8.5.0.0 == 8.0.1.0 == 8.0.1.1 == 8.5.5.0 == 8.0.1.3 == 8.5.0.1 == 8.0.0.0 == 8.0.1.2
CVE-2014-8913	Low	January 21, 2015 1/21/15	== 8.5.0.0 == 8.0.1.0 == 8.0.1.1 == 8.5.5.0 == 8.0.1.3 == 8.5.0.1 == 8.0.0.0 == 8.0.1.2
CVE-2014-6173	Low	December 19, 2014 12/19/14	== 8.5.0.0 == 8.0.1.0 == 8.0.1.1 == 8.5.5.0 == 8.0.1.3 == 8.5.0.1 == 8.0.0.0 == 8.0.1.2
CVE-2014-6182	Low	December 17, 2014 12/17/14	== 8.5.0.0 == 8.0.1.0 == 8.0.1.1 == 8.5.5.0 == 8.0.1.3 == 8.5.0.1 == 8.0.0.0 == 8.0.1.2
CVE-2014-4844	Medium	December 17, 2014 12/17/14	== 8.5.0.0 == 7.5.0.0 == 8.0.1.0 == 8.0.1.1 == 8.5.5.0 == 7.5.1.2 == 7.5.1.1 == 8.5.0.1 == 7.5.1.0 == 8.0.0.0 == 8.0.1.2 == 7.5.0.1
CVE-2014-6176	Low	December 16, 2014 12/16/14	== 8.5.5.0 == 8.5.0.1 == 8.0.1.3 == 7.5.0.0 == 7.5.1.0 == 7.5.0.1 == 7.5.1.1 == 8.0.0.0 == 8.0.1.2 == 8.5.0.0 == 8.0.1.1 == 8.0.1.0
CVE-2014-6101	Low	October 31, 2014 10/31/14	== 8.5.5.0 == 8.5.0.1 == 7.5.0.0 == 7.5.1.2 == 7.5.1.0 == 7.5.0.1 == 7.5.1.1 == 8.0.0.0 == 8.0.1.2 == 8.5.0.0 == 8.0.1.1 == 8.0.1.0
CVE-2014-4802	Low	October 7, 2014 10/7/14	== 8.5.0.0 == 8.0.1.0 == 8.0.1.1 == 8.5.5.0 == 8.0.1.3 == 8.5.0.1 == 8.0.0.0 == 8.0.1.2
CVE-2014-4758	Low	September 4, 2014 9/4/14	== 8.5.0.0 == 7.5.0.0 == 8.0.1.0 == 8.0.1.1 == 8.5.5.0 == 7.5.1.2 == 7.5.1.1 == 8.5.0.1 == 7.5.1.0 == 8.0.0.0 == 8.0.1.2 == 7.5.0.1
CVE-2014-4759	Low	September 4, 2014 9/4/14	== 8.5.0.0 == 8.5.5.0 == 8.5.0.1
CVE-2014-3075	Low	September 4, 2014 9/4/14	== 8.5.0.0 == 7.5.0.0 == 8.0.1.0 == 8.0.1.1 == 8.5.5.0 == 7.5.1.2 == 7.5.1.1 == 8.5.0.1 == 7.5.1.0 == 8.0.0.0 == 8.0.1.2 == 7.5.0.1
CVE-2014-3087	Low	August 17, 2014 8/17/14	== 8.5.0.0 == 7.5.0.0 == 8.0.1.0 == 8.0.1.1 == 8.5.5.0 == 7.5.1.2 == 7.5.1.1 == 8.5.0.1 == 7.5.1.0 == 8.0.0.0 == 8.0.1.2 == 7.5.0.1
CVE-2014-3076	Medium	August 11, 2014 8/11/14	== 8.5.0.0 == 8.5.5.0 == 8.5.0.1
CVE-2014-0957	Low	July 18, 2014 7/18/14	== 8.5.0.0 == 7.5.0.0 == 8.0.1.0 == 8.0.1.1 == 8.5.5.0 == 7.5.1.2 == 7.5.1.1 == 8.5.0.1 == 7.5.1.0 == 8.0.0.0 == 8.0.1.2 == 7.5.0.1
CVE-2014-0908	Medium	April 10, 2014 4/10/14	== 8.5.0.0 == 7.5.0.0 == 8.0.1.0 == 8.0.1.1 == 7.5.1.2 == 7.5.1.1 == 8.5.0.1 == 7.5.1.0 == 8.0.0.0 == 8.0.1.2 == 7.5.0.1
CVE-2013-0581	Low	July 6, 2013 7/6/13	== 8.0.1.0 == 7.5.1.1 == 7.5.1.0 == 8.0.0.0

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.