CVE-2023-4061 is a medium-severity (CVSS 6.5) Information Exposure vulnerability in org.wildfly.core:wildfly-controller. A fix is available for org.wildfly.core:wildfly-controller — see the affected versions and patch details below.
wildfly-core Exposure of Sensitive Information to an Unauthorized Actor vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-4061.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.wildfly.core:wildfly-controllerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wildfly.core:wildfly-controller | all versions | 22.0.0.Finalorg.wildfly.core:wildfly-controller:22.0.0.Final |
Affected Products
jboss enterprise application platformredhatwildfly coreredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.core:wildfly-controller, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wildfly.core:wildfly-controller to 22.0.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-4061 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability requires a malicious user to previously have access to the system, especially access to the HAL interface via browser and logged with a management user who have access to the resolve-expression method, hence the moderate impact.
Wildfly administrators are recommended to use Vault, especially the Elytron subsystem, to store potential critical information such as DNS, IPs, and credentials.Source: Red Hat security advisory for CVE-2023-4061 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss Enterprise Application Platform | org.wildfly.core/wildfly-controller:15.0.30.Final-redhat-00001 | RHSA-2023:5488 |
| Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8 | eap7-wildfly-0:7.4.13-8.GA_redhat_00001.1.el8eap | RHSA-2023:5485 |
| Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9 | eap7-wildfly-0:7.4.13-8.GA_redhat_00001.1.el9eap | RHSA-2023:5486 |
| Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7 | eap7-wildfly-0:7.4.13-8.GA_redhat_00001.1.el7eap | RHSA-2023:5484 |
Frequently Asked Questions
Is CVE-2023-4061 in your dependencies?
Find it across Maven, including transitive dependencies.