Credential disclosure via sensitive log entries
Published Dec 8, 2025 · Updated Dec 9, 2025
Sensitive information exposure in IBM Storage Defender Resiliency Service 2.0.0 through 2.0.18 allows remote authenticated users to read credentials. The affected service writes sensitive user credentials into log files, creating a secondary disclosure path outside the credential-handling workflow. Exploitation requires low-privileged network access to the affected service and access to the generated logs; IBM reports no integrity or service-interruption impact.
Summary
What happened
Sensitive information exposure in IBM Storage Defender Resiliency Service 2.0.0 through 2.0.18 allows remote authenticated users to read credentials. The affected service writes sensitive user credentials into log files, creating a secondary disclosure path outside the credential-handling workflow. Exploitation requires low-privileged network access to the affected service and access to the generated logs; IBM reports no integrity or service-interruption impact.
The record
- CVE
- CVE-2025-64650
- Published
- Dec 8, 2025
- Updated
- Dec 9, 2025
- Vendor
- IBM
- Product
- IBM Storage Defender Data Resiliency Service
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 2025CVE publishedPublication date reported by the CVE source.
- Dec 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <=2.0.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo