A flaw was found in the Wildfly Server Role Based Access Control (RBAC) provider. When authorization to control management operations is secured using the Role Based Access Control provider, a user without the required privileges can suspend or resume the server. A user with a Monitor or Auditor role is supposed to have only read access permissions and should not be able to suspend the server.
The vulnerability is caused by the Suspend and Resume handlers not performing authorization checks to validate whether the current user has the required permissions to proceed with the action.
Security readout for executives and security teams
Plain-English summary
An authenticated low-privilege WildFly management user may suspend or resume the server despite having a read-only Monitor or Auditor role. This can interrupt hosted applications and business services. The issue affects availability, not data confidentiality or integrity, according to the supplied CVSS assessment.
Executive priority
Schedule remediation promptly, prioritizing availability-critical application servers. Accelerate action where management interfaces are broadly reachable, credentials are shared, or Monitor and Auditor access is extensive. This is not presented as an unauthenticated takeover or data-theft issue.
Technical view
WildFly’s suspend and resume management handlers omit required authorization checks under the RBAC provider. A network-accessible user with limited management credentials can invoke availability-impacting operations without the intended permission. The supplied CVSS v3.1 score is 6.5: network reachable, low complexity, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure requires WildFly or JBoss EAP management access, RBAC authorization, and an authenticated low-privilege account. The bundle identifies affected package builds across EAP 7.4 and EAP 8.0 environments, but also contains product-level unaffected records. Confirm exposure against the applicable Red Hat advisory rather than relying only on product names.
Exploitation context
The flaw is remotely reachable through management operations but requires valid low-privilege credentials. Monitor or Auditor users are specifically relevant. The supplied record is not in KEV, and the sources provided do not establish active exploitation or a public working exploit.
Researcher notes
The affected-data mapping is internally complex: generic EAP 7 and EAP 8 entries are marked unaffected while specific builds and several seemingly unrelated package names are marked affected. The bundle also does not clarify the wildfly-core version-bound semantics. Use vendor advisories for authoritative package applicability and fixed-build determination.
Mitigation direction
Apply updates identified by the applicable Red Hat security advisory after compatibility testing.
Confirm exact affected builds and corrected packages using Red Hat guidance.
Restrict management interfaces to trusted administrative networks and authenticated operators.
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 · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
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-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.