GHSA-jw3v-5ch2-wfmm — wildfly-parent
MEDIUMGHSA-jw3v-5ch2-wfmm is a medium-severity (CVSS 5.3) CWE-209 vulnerability in org.wildfly:wildfly-parent. A fix is available for org.wildfly:wildfly-parent — see the affected versions and patch details below.
Wildfly logs plaintext passwords
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-jw3v-5ch2-wfmm plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.wildfly:wildfly-parentReal-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 discovered in WildFly before 21.0.0.Final where, Resource adapter logs plain text JMS password at warning level on connection error, inserting sensitive information in the log file.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wildfly:wildfly-parent | all versions | 21.0.0.Finalorg.wildfly:wildfly-parent:21.0.0.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly:wildfly-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wildfly:wildfly-parent to 21.0.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jw3v-5ch2-wfmm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jw3v-5ch2-wfmm can be triaged on real exposure rather than presence alone.
Tailored to GHSA-jw3v-5ch2-wfmm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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 Fuse 7.9 | wildfly | RHSA-2021:3140 |
| Red Hat JBoss Enterprise Application Platform 7 | wildfly | RHSA-2021:0250 |
| Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 6 | eap7-activemq-artemis-0:2.9.0-7.redhat_00017.1.el6eap | RHSA-2021:0246 |
| Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 7 | eap7-activemq-artemis-0:2.9.0-7.redhat_00017.1.el7eap | RHSA-2021:0247 |
| Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 8 | eap7-activemq-artemis-0:2.9.0-7.redhat_00017.1.el8eap | RHSA-2021:0248 |
| Red Hat Single Sign-On 7.4.5 | wildfly | RHSA-2021:0327 |
| Text-Only RHOAR | see advisory | RHSA-2021:0295 |
Frequently Asked Questions
Is GHSA-jw3v-5ch2-wfmm in your dependencies?
O3 Security finds GHSA-jw3v-5ch2-wfmm across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.