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

Total vulnerabilities in the database

Vulnerabilities for products matching "application_server"

Found 6 matching products. Filters apply to all results.

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

oracle / application_server

197 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2020-1967	High	April 21, 2020 4/21/20	== 12.1.3
CVE-2018-5407	Low	November 15, 2018 11/15/18	== 0.9.8 == 1.0.0 == 1.0.1
CVE-2018-0735	Medium	October 29, 2018 10/29/18	== 0.9.8 == 1.0.0 == 1.0.1
CVE-2010-0070	Low	January 13, 2010 1/13/10	== 10.1.3.4 == 10.1.2.3
CVE-2009-3412	Low	January 13, 2010 1/13/10	== 10.1.2.3
CVE-2010-0066	Medium	January 13, 2010 1/13/10	== 7.0.4.3 == 10.1.4.2
CVE-2010-0067	Medium	January 13, 2010 1/13/10	== 10.1.3.4 == 10.1.2.3
CVE-2009-3407	Low	October 22, 2009 10/22/09	== 10.1.2.3 == 10.1.4.2
CVE-2009-1990	Low	October 22, 2009 10/22/09	== 10.1.3.4.1
CVE-2009-1999	Low	October 22, 2009 10/22/09	*
CVE-2008-7233	High	September 14, 2009 9/14/09	== 1.1.8.26
CVE-2008-7234	Medium	September 14, 2009 9/14/09	== 10.1.2.2 == 10.1.3.3
CVE-2008-7235	Low	September 14, 2009 9/14/09	== 10.1.2.2
CVE-2008-7236	Low	September 14, 2009 9/14/09	== 10.1.2.2 == 10.1.3.1
CVE-2008-7237	Low	September 14, 2009 9/14/09	== 10.1.2.2 == 9.0.4.3
CVE-2009-0217	Medium	July 14, 2009 7/14/09	== 10.1.3.4 == 10.1.2.3 == 10.1.4.3im
CVE-2009-1976	Low	July 14, 2009 7/14/09	== 10.1.2.3
CVE-2009-1011	Low	April 15, 2009 4/15/09	== 8.2.2 == 8.3.0
CVE-2009-1017	Low	April 15, 2009 4/15/09	== 5.6.2 == 10.1.3.4 == 10.1.3.2.1 == 10.1.3.3.3
CVE-2009-0974	Low	April 15, 2009 4/15/09	== 10.1.2.3.0 == 10.1.4.2.0
CVE-2009-0983	Low	April 15, 2009 4/15/09	== 10.1.2.3.0 == 10.1.4.2.0
CVE-2009-0989	Medium	April 15, 2009 4/15/09	== 5.6.2 == 10.1.3.2.1 == 10.1.3.3.3
CVE-2009-0990	Medium	April 15, 2009 4/15/09	== 5.6.2 == 10.1.3.2.1 == 10.1.3.3.3
CVE-2009-0993	High	April 15, 2009 4/15/09	== 10.1.2.3.0
CVE-2009-0994	Low	April 15, 2009 4/15/09	== 5.6.2 == 10.1.3.4 == 10.1.3.2.1 == 10.1.3.3.3
CVE-2009-0996	Low	April 15, 2009 4/15/09	== 10.1.3.4 == 10.1.3.2.1 == 10.1.3.3.3
CVE-2009-1008	Low	April 15, 2009 4/15/09	== 8.2.2 == 8.3.0
CVE-2009-1009	Low	April 15, 2009 4/15/09	== 8.1.9
CVE-2009-1010	Low	April 15, 2009 4/15/09	== 8.2.2 == 8.3.0
CVE-2008-4014	Medium	January 14, 2009 1/14/09	== 10.1.2.2 == 10.1.2.0.2 == 7.0.4.4 == 9.0.2.1 == 10.1.3.2.0 == 10.1.3.1.0 == 10.1.2.1.0 == 9.0.2.0.0 == 1.0.2.2-r2 == 10.1.2.0.2-r2 == 1.0.2.0 == 10.1.3.3 == 9.0.4 == 11i == 10.1.0.3 == 10.1.2.0.0 == 9.0.2-r2 == 3.0.7 == 9.0.2.3 == 9.0.4.1 == 9.0.4.3 == 9.2.0.7 == 9.0.2.0.1 == 10.1.2.3 == 1.0 == 9.0.4.0 == 10.1.2.0.1 == 10.1.2.2.0 == 10.1.3.0.0 == 10.1.3 == 9.0.2.2 == 1.0.2.2.2 == 4.0 == 1.0.2.1s == 10.1.3.1 == 4.0.8.2 == 10.1.2.0 == 6.0.8.26_ps17 == 8.1.7 == 9.0.2 == 4.0.8 == 10.1.4.0.1 == 1.0.2.1 == 10.1.4.1 == 9.0.3 == 10.1.0.4 == 9.0.3.1 == 10.1.3.3.0 == 10.1.2_.0.1 == 10.1.2.0.1-r2 == 10.1.3.0 == 10.1.0.2 == 1.0.2.2-r1 == 10.1.2.1 == 10.1.2.0.0-r2 == 10.1.4.0 == 1.0.2.2 == 9.2.0.6 == 10.1.0.3.1 == 10.1.2 == 10.2.0.0 == 9.0.4.2 == 9.0 == 10.1.4.1.0 == 1.0.2
CVE-2008-4017	Medium	January 14, 2009 1/14/09	== 10.1.2.3
CVE-2008-5438	Low	January 14, 2009 1/14/09	== 10.1.2.3.0 == 10.1.4.2.0
CVE-2008-3986	Low	October 14, 2008 10/14/08	== 10.1.2.2 == 9.0.4.3
CVE-2008-3987	Low	October 14, 2008 10/14/08	== 10.1.2.3
CVE-2008-2619	Low	October 14, 2008 10/14/08	== 10.1.2.2 == 9.0.4.3 == 1.0.2.2
CVE-2008-3975	Medium	October 14, 2008 10/14/08	== 9.0.4.3 == 10.1.2.3
CVE-2008-3977	Medium	October 14, 2008 10/14/08	== 9.0.4.3 == 10.1.2.3
CVE-2008-2583	Low	July 15, 2008 7/15/08	*
CVE-2008-2589	Medium	July 15, 2008 7/15/08	== 10.1.2.2 == 9.0.4.3 == 10.1.4.1
CVE-2008-2593	Low	July 15, 2008 7/15/08	== 10.1.2.3.0 == 10.1.4.2.0
CVE-2008-2609	Medium	July 15, 2008 7/15/08	== 9.0.4.3
CVE-2008-2614	Low	July 15, 2008 7/15/08	== 10.1.3.3 == 9.0.4.3
CVE-2008-1812	High	April 16, 2008 4/16/08	== 9.0.4.3
CVE-2008-1814	High	April 16, 2008 4/16/08	== 10.1.2.2 == 9.0.4.3
CVE-2008-1824	High	April 16, 2008 4/16/08	== 10.1.2.2 == 10.1.3.3 == 9.0.4.3
CVE-2008-0340	High	January 17, 2008 1/17/08	== 10.1.2.0.2 == 10.1.3.1.0 == 10.1.2.1.0 == 9.0.4.3 == 10.1.2.2.0 == 10.1.3.0.0 == 10.1.3.3.0 == 1.0.2.2
CVE-2008-0343	High	January 17, 2008 1/17/08	== 10.1.2.0.2 == 10.1.3.1.0 == 10.1.2.1.0 == 9.0.4.3 == 10.1.2.2.0 == 10.1.3.0.0 == 10.1.3.3.0 == 1.0.2.2
CVE-2008-0344	High	January 17, 2008 1/17/08	== 10.1.2.0.2 == 10.1.3.1.0 == 10.1.2.1.0 == 9.0.4.3 == 10.1.2.2.0 == 10.1.3.0.0 == 10.1.3.3.0 == 1.0.2.2
CVE-2008-0345	High	January 17, 2008 1/17/08	== 10.1.2.0.2 == 10.1.3.1.0 == 10.1.2.1.0 == 9.0.4.3 == 10.1.2.2.0 == 10.1.3.0.0 == 10.1.3.3.0 == 1.0.2.2
CVE-2008-0346	High	January 17, 2008 1/17/08	== 10.1.2.0.2 == 10.1.3.1.0 == 10.1.2.1.0 == 9.0.4.3 == 10.1.2.2.0 == 10.1.3.0.0 == 10.1.3.3.0 == 1.0.2.2

hp / application_server

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2002-1856	Medium		December 31, 2002 12/31/02	== 8.0

multixtpm / application_server

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2007-5675	High		October 24, 2007 10/24/07	<= 4.0.2c

wso2 / application_server

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2017-14995	Low		October 4, 2017 10/4/17	== 5.3.0
CVE-2017-14651	Low		September 21, 2017 9/21/17	== 5.3.0

sap / application_server

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2020-6262	High		May 12, 2020 5/12/20	== 2008_1_620 == 2008_1_640 == 2008_1_700 == 2008_1_710 == 740 == 2008_1_46c

sitefusion / application_server

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2016-15023	Low		January 31, 2023 1/31/23	< 6.6.7

Showing vulnerabilities for 6 products matching "application_server". Each product has independent pagination.

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.