Security Resilience

CVE-2025-64650

Info Disclosure in Ibm Storage Defender Resiliency Service 2.0 – 2.0.18

Published
08 December 2025
Modified
07 October 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0027 18th percentile
Risk Priority 49 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-64650 is a medium-severity Insertion of Sensitive Information into Log File (CWE-532) vulnerability in Ibm Storage Defender Resiliency Service. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Credentials (T1589.001); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Storage Defender - Resiliency Service 2.0.0 through 2.0.18 could disclose sensitive user credentials in log files.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1589.001 Credentials Reconnaissance
Adversaries may gather credentials that can be used during targeting.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1654 Log Enumeration Discovery
Adversaries may enumerate system and service logs to find useful data.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38322Same product: Ibm Storage Defender Resiliency Service
CVE-2024-52361Same product: Ibm Storage Defender Resiliency Service
CVE-2023-50956Same product: Ibm Storage Defender Resiliency Service
CVE-2024-22312Same product: Ibm Storage Defender Resiliency Service
CVE-2023-50957Same product: Ibm Storage Defender Resiliency Service
CVE-2024-22313Same product: Ibm Storage Defender Resiliency Service
CVE-2024-47119Same product: Ibm Storage Defender Resiliency Service
CVE-2023-46171Same vendor: Ibm
CVE-2024-22352Same vendor: Ibm
CVE-2023-40682Same vendor: Ibm

Affected Assets

ibm
storage defender resiliency service
2.0 — 2.0.18

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-532

Procedures mandate excluding sensitive data from logs to prevent unauthorized exposure via audit records.

addresses: CWE-532

Identifies insertion of sensitive data into logs, allowing detection of unauthorized disclosure.

addresses: CWE-532

Cross-organizational coordination enables agreement on what data to include in audit logs, directly reducing insertion of sensitive information.

addresses: CWE-532

Identifying logging as a data action allows prevention of sensitive information being inserted into log files.

addresses: CWE-532

The process of identifying and eradicating spilled information applies directly to sensitive data inserted into log files.

addresses: CWE-532

Specific processing rules for sensitive PII categories commonly include restrictions on logging, making insertion of such data into log files less likely.

addresses: CWE-532

PIAs detect planned or existing logging of PII and require removal or protection, preventing insertion of sensitive information into logs.

addresses: CWE-532

Limits insertion of sensitive operational details into logs by treating such data as key information requiring protection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prohibit writing sensitive data to logs; eliminating the weakness satisfies only one narrow slice of the control.

PR.PS-04 partial match
blocks

Log generation configuration can and should exclude sensitive data, but the control statement focuses on availability rather than content filtering.

References