JBoss EJB Client information disclosure vulnerabilityGHSA-2259-h742-5vr4
MEDIUMGHSA-2259-h742-5vr4 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in org.jboss:jboss-ejb-client. A fix is available for org.jboss:jboss-ejb-client — see the affected versions and patch details below.
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.jboss:jboss-ejb-clientReal-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. The JBoss EJB client has publicly accessible privileged actions which may lead to information disclosure on the server it is deployed on. The highest threat from this vulnerability is to data confidentiality.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jboss:jboss-ejb-client | all versions | 4.0.39org.jboss:jboss-ejb-client:4.0.39 |
Affected Products
jboss enterprise application platform expansion packredhatjboss-ejb-clientredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss:jboss-ejb-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jboss:jboss-ejb-client to 4.0.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2259-h742-5vr4 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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat EAP-XP 2.0.0 via EAP 7.3.x base | jboss-ejb-client | RHSA-2021:2755 |
| Red Hat EAP-XP via EAP 7.3.x base | jboss-ejb-client | RHSA-2021:2210 |
| Red Hat JBoss Enterprise Application Platform 7 | jboss-ejb-client | RHSA-2021:0885 |
| Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 6 | eap7-activemq-artemis-0:2.9.0-9.redhat_00019.1.el6eap | RHSA-2021:0872 |
| Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 7 | eap7-activemq-artemis-0:2.9.0-9.redhat_00019.1.el7eap | RHSA-2021:0873 |
| Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 8 | eap7-activemq-artemis-0:2.9.0-9.redhat_00019.1.el8eap | RHSA-2021:0874 |
| Red Hat Single Sign-On 7.4.6 | jboss-ejb-client | RHSA-2021:0974 |
Frequently Asked Questions
Is GHSA-2259-h742-5vr4 in your dependencies?
Find it across Maven, including transitive dependencies.