dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2023-4061

MEDIUM · 6.5 CVSS v3.1 Published 2023-11-08
Fix available
A fix is available. Upgrade to 15.0.30 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 wildfly-core. A management user could use the resolve-expression in the HAL Interface to read possible sensitive information from the Wildfly system. This issue could allow a malicious user to access the system and obtain possible sensitive information from the system.

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 · moderate confidence

In WildFly Core, the HAL management console's resolve-expression feature allows authenticated management users to evaluate and resolve system expressions. This could be exploited to read sensitive information such as system properties, environment variables, or secrets that may be exposed through expression resolution, leading to information disclosure.

MitigationUpdate wildfly-core to the patched version that restricts or properly secures the resolve-expression functionality in the HAL interface, and review user permissions for management operations.

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:all versions= 7.4
Wildfly CoreApplication
Affected:< 15.0.30

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
High
Integrity
None
Availability
None

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

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 WildFly Core or JBoss EAP version
    Check the installed version by examining the 'wildfly-core' jar or the 'jboss-as-server' jar in the installation directory, or run the version command from the bin folder (e.g., ./bin/jboss-cli.sh --version or ./standalone.sh --version)
    Affected if The installed version is Wildfly Core < 15.0.30, or JBoss EAP version 7.4 (all versions are affected)
  2. Verify HAL management console is accessible
    Check if the management console is enabled and accessible via HTTP/HTTPS (default ports 9990 or 8443). Look for the 'hal-console'.war deployment or the management-interface configuration in standalone.xml/host.xml
    Affected if The HAL console is deployed and accessible on the management network
  3. Confirm resolve-expression feature availability
    Examine the HAL console's available operations or check the management model for 'resolve-expression' operation under the core-service=management/management-interface=http-interface section
    Affected if The resolve-expression operation is exposed and available to authenticated users
  4. Review management user access permissions
    Check the mgmt-users.properties or the configured identity store to determine which users have 'management' or 'superuser' roles that can access the HAL console and execute management operations
    Affected if There are authenticated management users with permissions to access the HAL console resolve-expression feature

You are affected if your environment runs WildFly Core < 15.0.30 or JBoss EAP 7.4 with the HAL management console accessible to authenticated users, as the resolve-expression feature can be exploited to disclose sensitive system properties, environment variables, or secrets.

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 15.0.30 or later
Fixed in 15.0.30
Interim mitigation

Update wildfly-core to the patched version that restricts or properly secures the resolve-expression functionality in the HAL interface, and review user permissions for management operations.

Recommended fix Moderate confidence

Wildfly Core 15.0.30 or later

  1. Upgrade Wildfly Core to version 15.0.30 or later to remediate the vulnerability in the HAL Interface resolve-expression function
  2. For JBoss Enterprise Application Platform, apply the corresponding patch or upgrade to a version that includes the fixed Wildfly Core 15.0.30
  3. Consult Red Hat's official documentation or support channels for version-specific guidance for JBoss EAP since all versions are reported as affected
  4. After upgrading, verify that the resolve-expression functionality in HAL console is properly restricted or operates within intended security boundaries
Caveat Review release notes for any breaking changes in Wildfly Core 15.0.30; for JBoss EAP, coordinate with Red Hat support for patch compatibility with your specific EAP version

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4061 — 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-2023-4061 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