Vulnerability Database

365,542

Total vulnerabilities in the database

Vulnerabilities for products matching "jboss_enterprise_application_platform"

Found 1 matching product.

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

redhat / jboss_enterprise_application_platform

597 vulnerabilities found
Title Severity Exploit Date Affected Version
High May 17, 2022 5/17/22
== 6.1.0
Medium May 17, 2022 5/17/22
<= 7.0.1
Medium May 17, 2022 5/17/22
== 7.0
High May 14, 2022 5/14/22
== 6.2.4
== 5.2.0
High May 14, 2022 5/14/22
== 6.3.0
High May 14, 2022 5/14/22
== 6.0.0
== 6.4.0
Medium May 14, 2022 5/14/22
== 7.1.0
High May 14, 2022 5/14/22
== 6.0.0
== 6.4.0
High May 13, 2022 5/13/22
== 3.0.7
== 3.0.8
== 3.1.0
== 3.1.1
== 3.1.2
== 3.1.4
== 3.1.5
== 3.2.3
== 3.2.4
== 3.2.5
== 3.2.9
== 3.2.13
== 3.3.0
== 3.5.1
Low May 13, 2022 5/13/22
== 4.2.0-cp09
== 4.3.0
== 5.1.1
High May 13, 2022 5/13/22
== 7.1.0
== 7.0.0
Medium May 13, 2022 5/13/22
== 7.0.0
High May 13, 2022 5/13/22
== 4.3.0-cp10
== 5.1.2
== 4.3.0
== 5.1.1
== 5.0.1
== 5.1.0
== 5.2.0
== 5.0.0
Critical May 13, 2022 5/13/22
== 4.3.0
== 6.0.0
== 5.0.0
Medium May 13, 2022 5/13/22
== 7.1
High May 13, 2022 5/13/22
== 7.1.0
Medium May 13, 2022 5/13/22
== 7.1
== 7.2
== 7.3
High May 13, 2022 5/13/22
== 6.0.0
== 6.4.0
== 7.0.0
== 7.1.0
High May 13, 2022 5/13/22
== 6.4.0
== 7.1.0
== 6.0.0
Medium May 13, 2022 5/13/22
== 5.0.0
Medium May 13, 2022 5/13/22
== 6.0.0
== 6.2.0
Medium May 13, 2022 5/13/22
== 6.0.0
== 6.2.0
Critical May 13, 2022 5/13/22
== 7.1
== 6.0.0
== 6.4.0
Critical May 13, 2022 5/13/22
== 5.2
== 6.4
== 7.0
High May 13, 2022 5/13/22
== 6.4
Critical May 13, 2022 5/13/22
== 6.4
Medium May 10, 2022 5/10/22
== 7.1.0
Medium April 22, 2022 4/22/22
== 5.0.0
High March 11, 2022 3/11/22
== 7.0.0
Medium February 10, 2022 2/10/22
== 7.3
== 7.4
== 7.2
High December 23, 2021 12/23/21
== 7.4.0-general_availability
== 7.3.9-general_availability
High December 14, 2021 12/14/21
== 6.0.0
== 7.0
Medium October 8, 2021 10/8/21
== 7.0.0
Medium June 15, 2021 6/15/21
== 7.3
== 7.4
Medium June 8, 2021 6/8/21
== 6.0.0
== 5.0.0
Medium June 4, 2021 6/4/21
== 7.2.0
== 7.3.0
High June 1, 2021 6/1/21
== 7.0.0
High May 28, 2021 5/28/21
== 5.0.0
Low May 25, 2021 5/25/21
== 7.0
High May 18, 2021 5/18/21
== 7.2.0
Medium April 30, 2021 4/30/21
== 7.2
== 7.3
== 7.4
High April 30, 2021 4/30/21
== 7.2
Medium April 30, 2021 4/30/21
== 7.3
== 7.4
== 7.2
High March 23, 2021 3/23/21
< 7.2.4
Medium October 16, 2020 10/16/20
< 5.0.3
Medium September 16, 2020 9/16/20
== 7.0.0
== 7.2.0
== 6.4.21
== 7.3.0
High September 9, 2020 9/9/20
== 6.0.0
High June 30, 2020 6/30/20
== 7.1
High June 15, 2020 6/15/20
== 7.2.0
Medium June 15, 2020 6/15/20
== 6.0.0
== 6.4.0
== 7.1.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.