dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2025-23367

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-30
Fix available
A fix is available. Upgrade to 7.4.21 / 8.0.7 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Wildfly Server RBAC provider has a missing authorization check in the Suspend and Resume management handlers. Users with Monitor or Auditor roles (which should have read-only access) can successfully invoke server suspend or resume operations because these handlers do not validate that the current user has the required permissions before executing the action.

MitigationApply the vendor patch to Wildfly that adds proper authorization checks to the Suspend and Resume handlers. As a compensating control, restrict Monitor and Auditor role assignments to trusted users only until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jboss Enterprise Application PlatformApplication
Affected:>= 7.4, < 7.4.21>= 8.0.0, < 8.0.7
WildflyApplication
Affected:< 27.0.1= 28.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Wildfly or JBoss EAP version
    Run the version command from the installation directory (e.g., $JBOSS_HOME/bin/jboss-cli.sh -c 'version' or check the manifest/product.conf file)
    Affected if The version is Wildfly < 27.0.1, Wildfly = 28.0.0, JBoss EAP >= 7.4 but < 7.4.21, or JBoss EAP >= 8.0.0 but < 8.0.7
  2. Confirm RBAC (Role-Based Access Control) is enabled
    Check the management interface configuration: look for <simple-role-decoder> or <role-decoder> elements in the mgmt-groups subsystem, or query via jboss-cli.sh: /core-service=management/access=authorization:read-children-names(child-type=role)
    Affected if RBAC is enabled and roles (particularly Monitor or Auditor) are configured
  3. Verify if Monitor or Auditor role users exist
    Query the management realm for assigned roles: /core-service=management/access=authorization/role=*:read-resource, or check the mgmt-groups users properties file for users mapped to Monitor or Auditor groups
    Affected if There are users assigned to Monitor or Auditor roles who can access the management interface
  4. Check management interface accessibility
    Confirm the management interface (HTTP at port 9990 or native at port 9999) is accessible to the Monitor/Auditor users, and verify they can reach the management API
    Affected if The management interface is network-accessible to users with Monitor or Auditor roles

A user is affected if they run a Wildfly version < 27.0.1 or = 28.0.0, or JBoss EAP 7.4.x/8.0.x within the affected ranges, with RBAC enabled and users assigned to Monitor or Auditor roles who can access the management interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.4.21 / 8.0.7 / 27.0.1 or later
Fixed in 7.4.218.0.727.0.1
Interim mitigation

Apply the vendor patch to Wildfly that adds proper authorization checks to the Suspend and Resume handlers. As a compensating control, restrict Monitor and Auditor role assignments to trusted users only until the patch is applied.

Recommended fix High confidence

WildFly 27.0.1 or JBoss EAP 7.4.21 / 8.0.7 depending on product in use

  1. 1. Identify the exact WildFly or JBoss EAP version currently running in your environment using the management console or CLI (e.g., /:version command)
  2. 2. For WildFly: Upgrade to WildFly 27.0.1 or later
  3. 3. For JBoss EAP 7.x: Upgrade to JBoss EAP 7.4.21 or later
  4. 4. For JBoss EAP 8.x: Upgrade to JBoss EAP 8.0.7 or later
  5. 5. After upgrading, verify that the RBAC configuration still functions correctly by testing with Monitor/Auditor role users to confirm they can no longer suspend or resume the server
  6. 6. Test server suspend and resume operations with appropriately privileged users (e.g., Administrator or SuperUser role) to ensure functionality is maintained
Caveat Minor: Ensure any existing scripts or automation relying on the (now-fixed) unauthorized suspend/resume behavior are updated; review role permissions post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23367 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data