Local credential disclosure via readable configuration files
Published Oct 16, 2025 · Updated Oct 16, 2025
Credential exposure in IBM Sterling B2B Integrator and File Gateway 6.2.0.0 through 6.2.0.5 and 6.2.1.0 allows local users to read stored credentials. The products write user credentials into configuration files that are readable by a local low-privileged account. IBM has not identified the specific files or credential types; exploitation requires local access and exposes credentials without changing data or interrupting service.
Summary
What happened
Credential exposure in IBM Sterling B2B Integrator and File Gateway 6.2.0.0 through 6.2.0.5 and 6.2.1.0 allows local users to read stored credentials. The products write user credentials into configuration files that are readable by a local low-privileged account. IBM has not identified the specific files or credential types; exploitation requires local access and exposes credentials without changing data or interrupting service.
The record
- CVE
- CVE-2025-36002
- Published
- Oct 16, 2025
- Updated
- Oct 16, 2025
- Vendor
- IBM
- Product
- IBM Sterling File Gateway
- Classifications
- CWE-256, CWE-260, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 16, 2025CVE publishedPublication date reported by the CVE source.
- Oct 16, 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=6.2.0.0 <=6.2.0.5
- Affected versionversion=6.2.1.0
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