LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25640: A flaw was discovered in WildFly before 21.0.0.Final where, Resource adapter logs plain text JMS password a...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

WildFly could write a JMS password into logs in clear text when a resource adapter connection error occurs. The main business risk is credential exposure through log files, especially if logs are centralized, broadly accessible, or retained for long periods.

Executive priority

Treat this as a credential hygiene and log exposure issue. It is not presented as actively exploited, but exposed JMS passwords can enable unauthorized access if logs were widely available or retained.

Technical view

CVE-2020-25640 is a CWE-209 information exposure issue in WildFly before 21.0.0.Final. On a resource adapter connection error, the AMQP/JMS resource adapter may log the JMS password at warning level, placing sensitive authentication material in application or infrastructure logs.

Likely exposure

Organizations using WildFly with JMS or AMQP resource adapters are most relevant. Exposure depends on whether connection errors occurred and whether logs are accessible to administrators, support staff, monitoring tools, or third-party log services.

Exploitation context

The provided sources do not indicate active exploitation, and the CVE is not listed as KEV. Exploitation would likely require access to affected logs rather than direct remote code execution.

Researcher notes

Evidence is clear on the logging behavior but incomplete on severity scoring. The bundle states WildFly before 21.0.0.Final, while the affected version entry is imprecise; validate exact fixed and affected versions with vendor records.

Mitigation direction

  • Check vendor guidance for the affected WildFly and resource adapter versions.
  • Upgrade away from affected WildFly versions where vendor guidance identifies a fixed release.
  • Rotate any JMS credentials that may have appeared in logs.
  • Restrict log access to personnel and systems with a clear operational need.
  • Review log retention and purge exposed credential material where policy permits.

Validation and detection

  • Inventory WildFly deployments and identify JMS or AMQP resource adapter usage.
  • Review warning-level logs for historical connection errors involving JMS credentials.
  • Confirm whether affected logs were forwarded to SIEM or log aggregation platforms.
  • Verify current WildFly and resource adapter versions against vendor advisories.
  • Check whether exposed JMS credentials have been rotated since the logging event.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-209: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-25640 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/awildflyWildfly 21.0.0.FinalListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-209 · source CWE mapping

Generation of Error Message Containing Sensitive Information

Generation of Error Message Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.