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

Found 1 matching product.

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

ibm / websphere_application_server

438 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2008-4283	High	February 10, 2009 2/10/09	== 5.0.0 == 5.1.0.5 == 5.0.2.10 == 5.1.1.14 == 5.0.2.5 == 5.0.2.1 == 5.1.1.2 == 5.0 == 5.0.2.11 == 5.1.1 == 5.1.1.6 == 5.1.0 == 5.0.1 == 5.0.2.3 == 5.0.2.15 == 5.1.1.15 == 5.1.1.3 == 5.1.1.13 == 5.0.2.12 == 5.1.1.10 == 5.0.2.8 == 5.1.1.17 == 5.1.1.7 == 5.1.0.4 == 5.0.2.16 == 5.1.0.2 == 5.1.1.18 == 5.0.2.2 == 5.1.1.1 == 5.0.2.9 == 5.0.2.6 == 5.0.2.13 == 5.1.1.12 <= 5.1.1.19 == 5.1.1.8 == 5.0.2.4 == 5.1.1.16 == 5.0.2 == 5.1.1.9 == 5.0.2.14 == 5.1.1.11 == 5.1.0.3 == 5.0.2.7 == 5.1.1.5 == 5.1.1.4
CVE-2008-4284	Medium	February 10, 2009 2/10/09	== 5.0.0 == 6.1.0.21 == 6.1.7 == 5.1.0.5 == 6.1 == 6.1.0.22 == 5.0.2.10 == 5.1.1.14 == 5.0.2.5 == 5.0.2.1 == 6.1.0.19 == 6.1.6 == 5.0 == 6.0.2.1 == 6.0.2.5 == 6.0.0.3 == 6.1.0.2 == 5.0.2.11 == 5.1.1 == 5.1.0 == 6.0.1.15 == 5.0.1 == 6.1.0.4 == 5.0.2.3 == 6.0.1.3 == 5.0.2.15 == 6.0.2.13 == 6.1.14 == 6.1.0.11 == 6.0.2.9 == 5.1.1.15 == 6.0.1.11 == 6.0.2.28 == 5.1.1.13 == 6.1.0.14 == 6.0.2.11 == 6.0.2.6 == 5.0.2.12 == 5.1.1.19 == 6.1.0.20 == 5.1.1.10 == 6.0.2.2 == 6.0.2 == 5.0.2.8 == 6.0.2.24 == 6.0.1.9 == 6.0.1.17 == 6.0.2.15 == 6.0.2.4 == 6.0.2.32 == 6.0.2.17 == 6.1.0.9 == 6.0.1.2 == 5.1.1.17 == 6.0.0.1 == 6.0.2.30 == 6.1.0.0 == 6.1.0.1 == 6.0.2.29 == 6.1.5 == 6.0.2.23 == 5.1.0.4 == 5.0.2.16 == 5.1.0.2 == 5.1.1.18 == 6.1.13 == 6.0.1 == 6.0.2.7 == 5.0.2.2 == 6.0.0.2 == 6.1.0.7 == 6.0.2.27 == 6.1.1 == 6.1.0.3 == 6.1.0.17 == 5.1.1.1 == 6.1.0.13 == 5.0.2.9 == 6.1.0.16 == 5.0.2.6 == 6.1.0.6 == 5.0.2.13 == 5.1.1.12 == 6.0.2.22 == 6.0.1.5 == 6.1.0.10 == 6.0.1.7 == 6.0 == 6.1.0.8 == 6.1.0.15 == 6.0.2.3 == 5.0.2.4 == 6.1.0.18 == 5.1.1.16 == 5.0.2 == 6.0.2.19 == 6.0.1.1 == 5.0.2.14 == 6.0.2.25 == 5.1.1.11 == 5.1.0.3 == 6.1.0 == 5.0.2.7 == 6.1.0.5 == 6.0.1.13 == 6.1.0.12 == 6.0.2.31 == 6.1.3
CVE-2009-0432	Medium	February 10, 2009 2/10/09	== 6.1.0.2 == 6.1.0.11 == 6.1.0.9 == 6.1.0.1 == 6.1.0.7 == 6.1.0.3 == 6.1.0.17 == 6.1.0.13 == 6.1.0.15 == 6.1.0.5
CVE-2009-0433	Low	February 10, 2009 2/10/09	== 5.1.0.5 == 6.1 == 5.1.1.14 == 6.0.2.1 == 6.0.2.5 == 6.0.0.3 == 6.1.0.2 == 5.1.1 == 5.1.0 == 6.0.1.15 == 6.1.0.4 == 6.0.1.3 == 6.0.2.13 == 6.1.0.11 == 6.0.2.9 == 5.1.1.15 == 6.0.1.11 == 6.0.2.28 == 5.1.1.13 == 6.1.0.14 == 6.0.2.11 == 6.0.2.6 == 5.1.1.19 == 5.1.1.10 == 6.0.2.2 == 6.0.2 == 6.0.2.24 == 6.0.1.9 == 6.0.1.17 == 6.0.2.15 == 6.0.2.4 == 6.0.2.17 == 6.1.0.9 == 6.0.1.2 == 5.1.1.17 == 6.0.0.1 == 6.1.0.0 == 6.1.0.1 == 6.0.2.23 == 5.1.0.4 == 5.1.0.2 == 5.1.1.18 == 6.0.1 == 6.0.2.7 == 6.0.0.2 == 6.1.0.7 == 6.0.2.27 == 6.1.0.3 == 6.1.0.17 == 5.1.1.1 == 6.1.0.13 == 6.1.0.16 == 6.1.0.6 == 5.1.1.12 == 6.0.2.22 == 6.0.1.5 == 6.1.0.10 == 6.0.1.7 == 6.0 == 6.1.0.8 == 6.1.0.15 == 6.0.2.3 == 6.1.0.18 == 5.1.1.16 == 6.0.2.19 == 6.0.1.1 == 6.0.2.25 == 5.1.1.11 == 5.1.0.3 == 6.1.0 == 6.1.0.5 == 6.0.1.13 == 6.1.0.12
CVE-2009-0434	Low	February 10, 2009 2/10/09	== 6.1.0.21 == 6.1 == 6.1.0.19 == 6.0.2.1 == 6.0.2.5 == 6.0.0.3 == 6.1.0.2 == 6.0.1.15 == 6.0.1.3 == 6.0.2.13 == 6.1.0.11 == 6.0.2.9 == 6.0.1.11 == 7.0 == 6.0.2.28 == 6.1.0.14 == 6.0.2.11 == 6.0.2.6 == 6.1.0.20 == 6.0.2.2 == 6.0.2 == 6.0.2.24 == 6.0.1.9 == 6.0.1.17 == 6.0.2.15 == 6.0.2.4 == 6.0.2.17 == 6.0.1.2 == 6.0.0.1 == 6.0.2.30 == 6.1.0.0 == 6.1.0.1 == 6.0.2.29 == 6.0.2.23 == 6.0.1 == 6.0.2.7 == 6.0.0.2 == 6.0.2.27 == 6.1.0.17 == 6.1.0.13 == 6.1.0.16 == 6.0.2.22 == 6.0.1.5 == 6.1.0.10 == 6.0.1.7 == 6.0 == 6.1.0.15 == 6.0.2.3 == 6.1.0.18 == 6.0.2.19 == 6.0.1.1 == 6.0.2.25 == 6.1.0 == 6.0.1.13 == 6.1.0.12 == 6.0.2.31
CVE-2009-0435	Medium	February 10, 2009 2/10/09	== 6.1.0 == 6.1.0.0 == 6.1.0.1 == 6.1.0.2 == 6.1.0.3 == 6.1.0.4 == 6.1.0.5 == 6.1.0.6 == 6.1.0.7 == 6.1.0.8 == 6.1.0.9 == 6.1.0.10 == 6.1.0.11 == 6.1.0.12 == 6.1.0.13 == 6.1.0.14 == 6.1.0.15 == 6.1.0.16 == 6.1.1 == 6.1.3 == 6.1.5 == 6.1.6 == 6.1.7 == 6.1.13 == 6.1.14
CVE-2009-0436	High	February 10, 2009 2/10/09	== 6.1 == 6.0.2.1 == 6.0.2.5 == 6.0.0.3 == 6.1.0.2 == 6.0.1.15 == 6.1.0.4 == 6.0.1.3 == 6.0.2.13 == 6.1.0.11 == 6.0.2.9 == 6.0.1.11 == 6.0.2.28 == 6.1.0.14 == 6.0.2.11 == 6.0.2.6 == 6.0.2.2 == 6.0.2 == 6.0.2.24 == 6.0.1.9 == 6.0.1.17 == 6.0.2.15 == 6.0.2.4 == 6.0.2.17 == 6.1.0.9 == 6.0.1.2 == 6.0.0.1 == 6.0.2.30 == 6.1.0.0 == 6.1.0.1 == 6.0.2.29 == 6.0.2.23 == 6.1.13 == 6.0.1 == 6.0.2.7 == 6.0.0.2 == 6.1.0.7 == 6.0.2.27 == 6.1.0.3 == 6.1.0.17 == 6.1.0.13 == 6.1.0.16 == 6.1.0.6 == 6.0.2.22 == 6.0.1.5 == 6.1.0.10 == 6.0.1.7 == 6.0 == 6.1.0.8 == 6.1.0.15 == 6.0.2.3 == 6.1.0.18 == 6.0.2.19 == 6.0.1.1 == 6.0.2.25 == 6.1.0 == 6.1.0.5 == 6.0.1.13 == 6.1.0.12
CVE-2009-0437	Low	February 10, 2009 2/10/09	== 6.0.2
CVE-2009-0438	Medium	February 10, 2009 2/10/09	== 7.0
CVE-2009-0391	High	February 2, 2009 2/2/09	== 6.0.1
CVE-2008-5411	Medium	December 10, 2008 12/10/08	<= 7.0
CVE-2008-5412	High	December 10, 2008 12/10/08	<= 7.0
CVE-2008-5413	Medium	December 10, 2008 12/10/08	<= 7.0
CVE-2008-5414	High	December 10, 2008 12/10/08	== 7.0
CVE-2008-4678	High	October 22, 2008 10/22/08	== 6.0.2.1 == 6.0.2.5 == 6.0.2.13 == 6.0.2.9 == 6.0.2.11 == 6.0.2.6 == 6.0.2.2 == 6.0.2 == 6.0.2.15 == 6.0.2.4 == 6.0.2.17 == 6.0.2.23 == 6.0.2.27 == 6.0.2.3 == 6.0.2.19 == 6.0.2.25
CVE-2008-4679	Medium	October 22, 2008 10/22/08	== 6.0.2.1 == 6.0.2.5 == 6.0.1.15 == 6.0.1.3 == 6.0.2.13 == 6.0.2.9 == 6.0.1.11 == 6.0.2.11 == 6.0.2.6 == 6.0.2.2 == 6.0.2 == 6.0.1.9 == 6.0.1.17 == 6.0.2.15 == 6.0.2.4 == 6.0.2.17 == 6.0.1.2 == 6.0.2.23 == 6.0.2.27 == 6.0.1.5 == 6.0.1.7 == 6.0.2.3 == 6.0.2.19 == 6.0.1.1 == 6.0.2.25 == 6.0.1.13
CVE-2008-4111	High	September 16, 2008 9/16/08	== 6.1 == 6.1.0.2 == 6.1.0.4 == 6.1.0.11 == 6.1.0.14 == 6.1.0.9 == 6.1.0.0 == 6.1.0.1 == 6.1.0.7 == 6.1.0.3 == 6.1.0.17 == 6.1.0.13 == 6.1.0.16 == 6.1.0.6 == 6.1.0.10 == 6.1.0.8 == 6.1.0.15 == 6.1.0.18 == 6.1.0 == 6.1.0.5 == 6.1.0.12
CVE-2008-3235	High	July 21, 2008 7/21/08	== 5.1.1.14 == 5.1.1.2 == 5.1.1 == 5.1.1.6 == 5.1.0 == 5.1.1.15 == 5.1.1.3 == 5.1.1.13 == 5.1.1.10 == 5.1.1.17 == 5.1.1.7 == 5.1.1.18 == 5.1.1.1 == 5.1.1.12 == 5.1.1.8 == 5.1.1.16 == 5.1.1.9 == 5.1.1.11 == 5.1.1.5 == 5.1.1.4
CVE-2008-3236	Medium	July 21, 2008 7/21/08	== 5.1.1.14 == 5.1.1.2 == 5.1.1 == 5.1.1.6 == 5.1.0 == 5.1.1.15 == 5.1.1.3 == 5.1.1.13 == 5.1.1.10 == 5.1.1.17 == 5.1.1.7 == 5.1.1.18 == 5.1.1.1 == 5.1.1.12 == 5.1.1.8 == 5.1.1.16 == 5.1.1.9 == 5.1.1.11 == 5.1.1.5 == 5.1.1.4
CVE-2008-2550	Medium	June 4, 2008 6/4/08	== 6.1 == 6.1.0.2 == 6.1.0.4 == 6.1.0.11 == 6.1.0.14 <= 6.1.0.16 == 6.1.0.9 == 6.1.0.0 == 6.1.0.1 == 6.1.0.7 == 6.1.0.3 == 6.1.0.13 == 6.1.0.6 == 6.1.0.10 == 6.1.0.8 == 6.1.0.15 == 6.1.0 == 6.1.0.5 == 6.1.0.12
CVE-2008-2221	High	May 14, 2008 5/14/08	== 5.0.2
CVE-2008-0740	Low	February 13, 2008 2/13/08	<= 6.0.2.24
CVE-2008-0741	High	February 13, 2008 2/13/08	<= 6.0.2.24
CVE-2008-0389	High	January 23, 2008 1/23/08	== 6.1.7 == 6.1 == 5.1.1.14 == 5.1.1.2 == 6.1.6 == 6.0.2.1 == 6.0.2.5 == 5.1.1 == 5.1.1.6 == 6.0.2.13 == 6.1.14 == 6.0.2.9 == 5.1.1.15 == 5.1.1.3 == 6.0.2.11 == 5.1.1.10 == 6.0.2 == 6.0.2.24 == 6.1.5 == 5.1.1.7 == 6.0.2.23 == 6.1.13 == 6.0.1 == 6.0.2.7 == 6.1.1 == 5.1.1.1 == 5.1.1.12 == 6.0.2.22 == 5.1.1.8 == 6.0 == 6.0.2.3 == 5.1.1.16 == 6.0.2.19 == 5.1.1.9 == 6.0.2.25 <= 5.1.1.17 == 5.1.1.5 == 5.1.1.4 == 6.1.3
CVE-2007-6679	High	January 10, 2008 1/10/08	== 6.1 == 6.1.0.2 == 6.1.0.11 == 6.1.0.9 == 6.1.0.1 == 6.1.0.7 == 6.1.0.3 <= 6.0.2.24 == 6.1.0.5
CVE-2007-5944	Low	November 14, 2007 11/14/07	== 5.1.1.14 == 5.1.1.6 == 5.1.1.15 == 5.1.1.13 == 5.1.1.10 == 5.1.1.7 == 5.1.1.12 == 5.1.1.8 == 5.1.1.16 == 5.1.1.9 == 5.1.1.11 == 5.1.1.5 == 5.1.1.4
CVE-2007-5798	Low	November 3, 2007 11/3/07	<= 6.1.0.12
CVE-2007-5799	Low	November 3, 2007 11/3/07	<= 6.1.0.12
CVE-2007-5483	High	October 16, 2007 10/16/07	== 5.1.1.14 == 5.1.1.2 == 6.0.2.1 == 6.0.2.5 == 6.0.0.3 == 5.1.1 == 5.1.1.6 == 6.0.2.13 == 6.0.2.9 == 5.1.1.3 == 6.0.2.11 == 6.0.2.6 == 5.1.1.10 == 6.0.2.2 == 6.0.2 == 6.0.2.15 == 6.0.2.4 == 6.0.2.17 == 6.0.1.2 == 6.0.0.1 == 5.1.1.7 == 6.0.1 == 6.0.2.7 == 6.0.0.2 == 5.1.1.1 == 5.1.1.12 == 5.1.1.8 == 6.0 == 6.0.2.3 == 6.0.2.19 == 5.1.1.9 == 5.1.1.5 == 5.1.1.4
CVE-2007-4833	Medium	September 12, 2007 9/12/07	<= 6.1.0.9
CVE-2007-4839	High	September 12, 2007 9/12/07	== 6.1.0.9
CVE-2007-3960	High	July 24, 2007 7/24/07	<= 6.0.2.19
CVE-2007-3397	Medium	June 26, 2007 6/26/07	== 6.0.2.1 == 6.0.2.5 == 6.1.0.2 == 6.0.2.13 == 6.0.2.9 == 6.0.2.11 == 6.0.2.6 == 6.0.2.2 == 6.0.2 == 6.0.2.15 == 6.0.2.4 == 6.0.2.17 == 6.1.0.1 == 6.0.2.7 == 6.1.0.7 == 6.1.0.3 == 6.0.2.3 == 6.0.2.19 == 6.1.0 == 6.1.0.5
CVE-2007-3262	High	June 19, 2007 6/19/07	<= 6.1.0.7
CVE-2007-3263	High	June 19, 2007 6/19/07	<= 6.1.0.7
CVE-2007-3264	High	June 19, 2007 6/19/07	<= 6.1.0.7
CVE-2007-3265	Low	June 19, 2007 6/19/07	<= 6.1.0.7
CVE-2006-7198	High	April 30, 2007 4/30/07	== 5.1.1.14 <= 6.0.2.11
CVE-2007-1944	Medium	April 11, 2007 4/11/07	<= 6.1.0.1
CVE-2007-1945	High	April 11, 2007 4/11/07	<= 6.1.0.1
CVE-2007-1608	High	March 22, 2007 3/22/07	<= 6.0.2.15
CVE-2006-7164	Low	March 20, 2007 3/20/07	== 5.0.1 == 5.0.2 == 5.0.2.1 == 5.0.2.2 == 5.0.2.3 == 5.0.2.4 == 5.0.2.5 == 5.0.2.6 == 5.0.2.7 == 5.0.2.8 == 5.0.2.9 == 5.0.2.10 == 5.0.2.11 == 5.0.2.12 == 5.0.2.13 == 5.0.2.14 == 5.0.2.15 == 5.0.2.16
CVE-2006-7165	Low	March 20, 2007 3/20/07	== 5.1.0.5 == 5.1.1 == 5.1.0 == 5.1.0.4 == 5.1.0.2 == 5.1.0.3
CVE-2006-7166	Medium	March 20, 2007 3/20/07	== 5.1.0.5 == 5.0.2.10 == 5.0.2.5 == 5.0.2.1 == 5.1.1.2 == 5.0 == 5.0.2.11 == 5.1.1 == 5.1.1.6 == 5.1.0 == 5.0.1 == 5.0.2.3 == 5.0.2.15 == 5.1.1.3 == 5.0.2.12 == 5.0.2.8 == 5.1.1.7 == 5.1.0.4 == 5.0.2.16 == 5.1.0.2 == 5.0.2.2 == 5.1.1.1 == 5.0.2.9 == 5.0.2.6 == 5.0.2.13 == 5.1.1.8 == 5.0.2.4 == 5.0.2 == 5.1.1.9 == 5.0.2.14 == 5.1.0.3 == 5.0.2.7 == 5.1.1.5 == 5.1.1.4
CVE-2006-6636	High	December 19, 2006 12/19/06	== 5.1.1.2 == 6.0.2.1 == 6.0.2.5 == 5.1.1 == 5.1.1.6 == 6.0.2.13 == 6.0.2.9 == 5.1.1.3 == 6.0.2.11 == 5.1.1.10 == 6.0.2.15 == 5.1.1.7 == 6.0.2.7 == 5.1.1.1 == 5.1.1.12 == 5.1.1.8 == 6.0.2.3 == 5.1.1.9 == 5.1.1.5 == 5.1.1.4
CVE-2006-6637	Medium	December 19, 2006 12/19/06	== 6.0.2.1 == 6.0.2.5 == 6.0.2.13 == 6.0.2.9 == 6.0.2.11 == 6.0.2.15 == 6.0.2.7 == 6.0.2.3
CVE-2006-6135	High	November 28, 2006 11/28/06	== 6.1.0
CVE-2006-6136	High	November 28, 2006 11/28/06	== 6.1.0
CVE-2006-5323	High	October 17, 2006 10/17/06	<= 6.1.0.1
CVE-2006-5324	High	October 17, 2006 10/17/06	<= 6.1.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.