A flaw was found in JBoss Enterprise Application Platform. When role-based authorization is used for Enterprise Java Beans (EJB) access, the system does not correctly call the necessary authorization modules. This prevents Java Authorization Contract for Containers (JACC) permissions from being applied, allowing remote attackers to gain unauthorized access to EJBs.
Security readout for executives and security teams
Plain-English summary
This flaw can let a remote attacker access Enterprise Java Beans that should be protected by role-based authorization. The issue is business-relevant where legacy Red Hat JBoss EAP 6 systems still expose EJB services, because access controls may not be enforced as expected.
Executive priority
Prioritize remediation if any legacy JBoss EAP 6 system still supports business-critical EJB services or is reachable by untrusted networks. For retired, isolated, or non-EJB deployments, treat as a targeted legacy cleanup item.
Technical view
JBoss EAP failed to correctly invoke required authorization modules for role-based EJB access. As a result, JACC permissions may not be applied, creating an authorization bypass mapped to CWE-280. The CVSS 3.1 score is 5.3, network-accessible, low attack complexity, no privileges, and confidentiality impact only.
Likely exposure
Exposure is most likely in legacy Red Hat JBoss Enterprise Application Platform 6 deployments, especially affected EAP 6 packages for RHEL 5 listed in the source bundle. Systems without EJB remote access or without affected package versions are less likely to be exposed.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The vulnerability is remotely reachable and requires no privileges or user interaction per CVSS, but the documented impact is limited to unauthorized EJB access and low confidentiality impact.
Researcher notes
The source bundle identifies authorization-module bypass and missing JACC permission application, but does not include exploit details or exact fixed package versions. Use Red Hat’s CVE page and RHSA advisories as authoritative references for package-level status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-280: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-280 · source CWE mapping
Improper Handling of Insufficient Permissions or Privileges
Improper Handling of Insufficient Permissions or Privileges represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.