WildflyApplication · Redhat
CVE-2020-25640
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 · uneditedA 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.
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 confidenceIn WildFly versions before 21.0.0.Final, the JMS resource adapter logs JMS passwords in plain text at the WARNING log level when a connection error occurs, exposing sensitive credentials in log files.
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
WildflyApplication
< 21.0.0CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed WildFly versionCheck the version banner displayed when WildFly starts, or look for version info in the $WILDFLY_HOME/bin/launch.sh script, or query the management interface using: ./jboss-cli.sh 'core-service=server-environment' read-attribute=name=product-versionAffected if The installed version is WildFly before 21.0.0.Final (any 20.x.x or earlier release)
-
Identify if JMS resource adapter is deployedCheck for deployed JMS resource adapter files in $WILDFLY_HOME/standalone/deployments/ or via management CLI: ./jboss-cli.sh 'subsystem=resource-adapters' lsAffected if A JMS resource adapter (such as activemq-rar.rar or generic-ra.rar) is deployed and configured in the resource-adapters subsystem
-
Check logging configuration for WARNING levelReview standalone.xml or domain.xml under <subsystem xmlns="urn:jboss:domain:logging:..."> to see if the root logger or org.jboss.jms console handler is set to WARNING, DEBUG, or TRACE level. Use: ./jboss-cli.sh 'subsystem=logging' read-attribute(name=root-logger-level)Affected if Logging is configured at WARNING, DEBUG, or TRACE level, which would capture the plaintext password messages
-
Search logs for exposed credentialsSearch WildFly log files (typically in $WILDFLY_HOME/standalone/log/ or /var/log/wildfly/) for patterns matching passwords in plain text. Use: grep -r "password" /path/to/logs/*.log | grep -i "jms"Affected if Log files contain plaintext JMS passwords in the context of connection errors or warnings
A user is affected if they run WildFly versions before 21.0.0.Final, have a JMS resource adapter configured, and their logging level captures WARNING messages, potentially exposing JMS credentials in log files.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data21.0.0
Upgrade WildFly to version 21.0.0.Final or later to receive the fix. Additionally, audit and rotate any JMS passwords that may have been exposed in logs, and review log file access controls.
Fix this in Wildfly
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2020-25640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-25640 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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