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.

325,773

Total vulnerabilities in the database

Vulnerabilities for products matching "db2"

Found 1 matching product.

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

ibm / db2

323 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2011-0757	Medium	February 2, 2011 2/2/11	== 9.1-fp4 == 9.1-fp6a == 9.1-fp1 == 9.1 == 9.1-fp5 == 9.1-fp3 == 9.1-fp7a == 9.1-fp3a == 9.1-fp2a == 9.1-fp6 <= 9.1 == 9.1-fp8 == 9.1-fp2 == 9.1-fp4a == 9.1-fp7 == 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a <= 9.5 == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a <= 9.7 == 9.7
CVE-2011-0731	High	February 1, 2011 2/1/11	== 9.1-fp4 == 9.1-fp6a == 9.1-fp1 == 9.1 == 9.1-fp5 == 9.1-fp3 == 9.1-fp7a == 9.1-fp3a == 9.1-fp2a == 9.1-fp6 <= 9.1 == 9.1-fp8 == 9.1-fp2 == 9.1-fp4a == 9.1-fp7 == 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp6 <= 9.5 == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a <= 9.7 == 9.7-fp1 == 9.7
CVE-2010-3733	High	October 5, 2010 10/5/10	== 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3734	Medium	October 5, 2010 10/5/10	== 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3735	Low	October 5, 2010 10/5/10	== 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3736	Low	October 5, 2010 10/5/10	== 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3737	Low	October 5, 2010 10/5/10	== 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3738	Medium	October 5, 2010 10/5/10	== 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3740	Low	October 5, 2010 10/5/10	== 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3731	High	October 5, 2010 10/5/10	== 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3732	Low	October 5, 2010 10/5/10	== 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3474	Medium	September 20, 2010 9/20/10	== 9.7.0.1 == 9.7.0.2 == 9.7
CVE-2010-3475	Low	September 20, 2010 9/20/10	== 9.7.0.1 == 9.7.0.2 == 9.7
CVE-2010-3193	High	August 31, 2010 8/31/10	== 9.1-fp4 == 9.1-fp6a == 9.1-fp1 == 9.1 == 9.1-fp5 == 9.1-fp3 == 9.1-fp7a == 9.1-fp3a == 9.1-fp2a == 9.1-fp6 == 9.1-fp8 == 9.1-fp2 == 9.1-fp4a == 9.1-fp7 == 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.7-fp1 == 9.5-fp3b == 9.5-fp2 == 9.7 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3194	High	August 31, 2010 8/31/10	== 9.1-fp4 == 9.1-fp6a == 9.1-fp1 == 9.1 == 9.1-fp5 == 9.1-fp3 == 9.1-fp7a == 9.1-fp3a == 9.1-fp2a == 9.1-fp6 == 9.1-fp8 == 9.1-fp2 == 9.1-fp4a == 9.1-fp7 == 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.7-fp1 == 9.5-fp3b == 9.5-fp2 == 9.7 == 9.5-fp3 == 9.5-fp3a
CVE-2010-3195	Medium	August 31, 2010 8/31/10	== 9.1-fp6a == 9.1-fp1 == 9.1-fp4 == 9.1 == 9.1-fp5 == 9.1-fp3 == 9.1-fp7a == 9.1-fp3a == 9.1-fp2a == 9.1-fp8 == 9.1-fp2 == 9.1-fp4a == 9.1-fp6 == 9.1-fp7 == 9.5-fp3 == 9.5-fp3a == 9.5-fp3b == 9.5-fp2 == 9.5-fp2a == 9.5-fp1 == 9.5 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.7 == 9.7-fp1
CVE-2010-3196	Low	August 31, 2010 8/31/10	== 9.7-fp1 == 9.7
CVE-2010-3197	Medium	August 31, 2010 8/31/10	== 9.7-fp1 == 9.7
CVE-2010-1560	Low	April 27, 2010 4/27/10	== 9.1-fp4 == 9.1-fp6a == 9.1-fp1 == 9.1-fp5 == 9.1-fp3 == 9.1-fp7a == 9.1-fp3a == 9.1-fp6 == 9.1-fp2 == 9.1-fp4a == 9.1-fp7 <= 9.1
CVE-2010-0472	Medium	February 2, 2010 2/2/10	== 9.7.0.1
CVE-2010-0462	Medium	January 28, 2010 1/28/10	== 9.1-fp4 == 9.5 == 9.1-fp6a == 9.1-fp1 == 9.5-fp4 == 9.5-fp5 == 9.5-fp4a == 9.1 == 9.1-fp5 == 9.5-fp1 == 9.1-fp3 == 9.1-fp7a == 9.1-fp3a == 9.1-fp2a == 9.5-fp2a == 9.1-fp6 == 9.7-fp1 == 9.1-fp8 == 9.1-fp2 == 9.1-fp4a == 9.5-fp3b == 9.5-fp2 == 9.7 == 9.1-fp7 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4438	Medium	December 28, 2009 12/28/09	== 9.1-fp4 == 9.1-fp6a == 9.1-fp1 == 9.5-fp4 == 9.5-fp4a == 9.1-fp5 == 9.5-fp1 == 9.1-fp3 == 9.1-fp3a == 9.5-fp2a == 9.1-fp6 == 9.1-fp2 == 9.1-fp4a == 9.5-fp3b == 9.5-fp2 == 9.7 == 9.1-fp7 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4439	Low	December 28, 2009 12/28/09	== 9.5-fp4 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4325	Medium	December 16, 2009 12/16/09	== 8.2-fp12 == 8.2-fp7 == 9.1-fp4 == 9.5 == 9.1-fp6a == 9.1-fp1 == 8.2-fp17 == 8.2-fp5 == 8.2-fp3 == 8.2-fp8 == 8.2-fp14 == 9.1 == 8.2-fp2 == 9.1-fp5 == 8.2-fp9 == 9.5-fp1 == 8.2-fp13 == 9.1-fp3 == 8.2-fp15 == 9.1-fp3a == 9.5-fp2a == 9.1-fp6 == 8.2-fp10 == 8.2-fp16 == 8.2-fp6 == 9.1-fp2 == 9.1-fp4a == 9.5-fp3b == 9.5-fp2 == 9.7 == 8.2-fp11 == 9.1-fp7 == 9.5-fp3 == 9.5-fp3a == 8.2-fp1 == 8.2 == 8.2-fp4
CVE-2009-4326	Low	December 16, 2009 12/16/09	== 9.5 == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.7 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4327	Medium	December 16, 2009 12/16/09	== 9.5 == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.7 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4328	Low	December 16, 2009 12/16/09	== 9.5 == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4329	Low	December 16, 2009 12/16/09	== 9.5 == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4330	High	December 16, 2009 12/16/09	== 9.5 == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4331	High	December 16, 2009 12/16/09	== 9.5 == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.7 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4332	Medium	December 16, 2009 12/16/09	== 9.1-fp4 == 9.5 == 9.1-fp6a == 9.1-fp1 == 9.1 == 9.1-fp5 == 9.5-fp1 == 9.1-fp3 == 9.1-fp3a == 9.5-fp2a == 9.1-fp6 == 9.1-fp2 == 9.1-fp4a == 9.5-fp3b == 9.5-fp2 == 9.7 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4333	High	December 16, 2009 12/16/09	== 9.5 == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4334	Low	December 16, 2009 12/16/09	== 9.1-fp4 == 9.5 == 9.1-fp6a == 9.1-fp1 == 9.1 == 9.1-fp5 == 9.5-fp1 == 9.1-fp3 == 9.1-fp3a == 9.5-fp2a == 9.1-fp6 == 9.1-fp2 == 9.1-fp4a == 9.5-fp3b == 9.5-fp2 == 9.7 == 9.1-fp7 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4335	High	December 16, 2009 12/16/09	== 9.5 == 9.5-fp4 == 9.5-fp4a == 9.5-fp1 == 9.5-fp2a == 9.5-fp3b == 9.5-fp2 == 9.5-fp3 == 9.5-fp3a
CVE-2009-4150	Low	December 2, 2009 12/2/09	== 9.1-fp4 == 9.1-fp6a == 9.1-fp1 == 9.1-fp5 == 9.5-fp1 == 9.1-fp3 == 9.1-fp3a == 9.1-fp6 == 9.1-fp2 == 9.5-fp2 == 9.7 == 9.1-fp7 == 9.5-fp3
CVE-2009-3471	High	September 29, 2009 9/29/09	== 8.0-fp11 == 8.0-fp3 == 8.0-fp10 == 9.1-fp4 == 9.1-fp1 == 8.0-fp9 == 8.0-fp4 == 9.1-fp5 == 9.5-fp1 == 8.0-fp16 == 9.1-fp3 == 8.0-fp6 == 8.0-fp8 == 8.0-fp14 == 9.1-fp6 == 8.0-fp2 == 8.0-fp1 == 8.0-fp5 == 8.0-fp17 == 9.1-fp2 == 8.0-fp13 == 9.5-fp2 == 9.1-fp7 == 8.0-fp12 == 9.5-fp3 == 8.0-fp15 == 8.0-fp7
CVE-2009-3472	Medium	September 29, 2009 9/29/09	== 8.0-fp11 == 8.0-fp3 == 8.0-fp10 == 9.1-fp4 == 9.1-fp1 == 8.0-fp9 == 8.0-fp4 == 9.1-fp5 == 9.5-fp1 == 8.0-fp16 == 9.1-fp3 == 8.0-fp6 == 8.0-fp8 == 8.0-fp14 == 9.1-fp6 == 8.0-fp2 == 8.0-fp1 == 8.0-fp5 == 8.0-fp17 == 9.1-fp2 == 8.0-fp13 == 9.5-fp2 == 9.1-fp7 == 8.0-fp12 == 9.5-fp3 == 8.0-fp15 == 8.0-fp7
CVE-2009-3473	High	September 29, 2009 9/29/09	== 9.1-fp4 == 9.1-fp1 == 9.1-fp5 == 9.1-fp3 == 9.1-fp6 == 9.1-fp2 == 9.1-fp7
CVE-2009-2858	Medium	August 19, 2009 8/19/09	== 8.1-fp1 == 8.1-fp10 == 8.1-fp6c == 8.1-fp2 <= 8.1 == 8.1-fp5 == 8.1-fp8 == 8.1-fp8a == 8.1-fp14 == 8.1-fp11 == 8.1-fp7 == 8.1-fp6b == 8.1-fp17a == 8.1-fp15 == 8.1-fp9a == 8.1-fp12 == 8.1-fp4 == 8.1-fp4a == 8.1-fp6 == 8.1-fp13 == 8.1-fp3 == 8.1-fp7a == 8.1-fp9 == 8.1-fp6a
CVE-2009-2859	Low	August 19, 2009 8/19/09	== 8.1-fp1 == 8.1-fp10 == 8.1-fp6c == 8.1-fp2 <= 8.1 == 8.1-fp5 == 8.1-fp8 == 8.1-fp8a == 8.1-fp14 == 8.1-fp11 == 8.1-fp7 == 8.1-fp6b == 8.1-fp17a == 8.1-fp15 == 8.1-fp9a == 8.1-fp12 == 8.1-fp4 == 8.1-fp4a == 8.1-fp6 == 8.1-fp13 == 8.1-fp3 == 8.1-fp7a == 8.1-fp9 == 8.1-fp6a
CVE-2009-2860	Medium	August 19, 2009 8/19/09	== 8.1-fp1 == 8.1-fp10 == 8.1-fp6c == 8.1-fp2 <= 8.1 == 8.1-fp5 == 8.1-fp8 == 8.1-fp8a == 8.1-fp14 == 8.1-fp11 == 8.1-fp7 == 8.1-fp6b == 8.1-fp17a == 8.1-fp15 == 8.1-fp9a == 8.1-fp12 == 8.1-fp4 == 8.1-fp4a == 8.1-fp6 == 8.1-fp13 == 8.1-fp3 == 8.1-fp7a == 8.1-fp9 == 8.1-fp6a
CVE-2008-2154	Medium	June 3, 2009 6/3/09	== 8.0-fp11 == 8.0-fp10 == 9.1-fp4 == 9.1-fp1 == 9.5-fp1 == 8.0-fp16 == 9.1-fp3 == 9.1-fp3a == 8.0-fp14 == 8.0-fp1 == 9.1-fp2 == 9.1-fp4a == 8.0-fp13 == 8.0-fp12 == 8.0-fp15
CVE-2008-6820	High	June 3, 2009 6/3/09	== 8.0-fp11 == 8.0-fp10 == 8.0-fp14 == 8.0-fp1 == 8.0-fp16 == 8.0-fp13 == 8.0-fp12 == 8.0-fp15 == 9.1-fp3 == 9.1-fp3a == 9.1-fp2 == 9.1-fp4a == 9.1-fp4 == 9.1-fp1 == 9.5-fp1
CVE-2008-6821	High	June 3, 2009 6/3/09	== 8.0-fp11 == 8.0-fp10 == 9.1-fp4 == 9.1-fp1 == 9.5-fp1 == 8.0-fp16 == 9.1-fp3 == 9.1-fp3a == 8.0-fp14 == 8.0-fp1 == 9.1-fp2 == 9.1-fp4a == 8.0-fp13 == 8.0-fp12 == 8.0-fp15
CVE-2009-1905	Low	June 3, 2009 6/3/09	== 8.0-fp11 == 8.0-fp10 == 9.1-fp1 <= 9.1 == 9.1-fp3 == 8.0-fix_pack15 == 9.1-fp3a == 8.0-fp14 <= 8.0 == 8.0-fp1 == 9.1-fp2 <= 9.5 == 9.1-fp4a == 8.0-fp13 == 8.0-fp12 == 8.0-fp15
CVE-2009-1906	Low	June 3, 2009 6/3/09	== 9.1-fp4 == 9.1-fp6a == 9.1-fp1 == 9.1-fp5 == 9.5-fp1 == 9.1-fp3 == 9.1-fp3a == 9.1-fp6 == 9.1-fp2 == 9.1-fp4a == 9.5-fp2 == 9.5-fp3
CVE-2009-1239	Medium	April 3, 2009 4/3/09	== 9.1-fp4 == 9.1-fp1 == 9.1 == 9.1-fp5 == 9.1-fp3 <= 9.1 == 9.1-fp3a == 9.1-fp6 == 9.1-fp2 == 9.1-fp4a
CVE-2008-4691	Medium	October 22, 2008 10/22/08	== 9.1-fp4 == 9.1-fp1 == 9.1 == 9.1-fp3 == 9.1-fp3a <= 9.1 == 9.1-fp2 == 9.1-fp4a
CVE-2008-4692	High	October 22, 2008 10/22/08	== 8.0-fp11 == 8.0-fp3 == 8.0-fp10 == 9.1-fp4 == 9.5 == 9.1-fp1 == 8.0-fp9 == 8.0-fp7b == 8.0-fp6a == 8.0-fp9a == 9.1 == 8.0-fp4 == 9.1-fp3 == 8.0-fp7a == 8.0-fp6 == 9.1-fp3a == 8.0-fp8 == 8.0-fp14 <= 9.1 == 8.0-fp2 <= 8.0 == 8.0-fp1 == 8.0-fp4a == 8.0-fp5 == 9.1-fp2 <= 9.5 == 8.0-fp6c == 9.1-fp4a == 8.0-fp13 == 8.0-fp8a == 8.0-fp12 == 8.0-fp6b == 8.0-fp15 == 8.0-fp7
CVE-2008-4693	Medium	October 22, 2008 10/22/08	== 9.1-fp4 == 9.5 == 9.1-fp1 == 9.1 == 9.1-fp3 == 9.1-fp3a <= 9.1 == 9.1-fp2 <= 9.5 == 9.1-fp4a

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.