Sensitive information disclosure via detailed error messages
Published Jan 25, 2025 · Updated Jan 27, 2025
Sensitive information disclosure in IBM Sterling Control Center 6.2.1 and 6.3.1 allows remote authenticated users to read browser error details. The web interface returns detailed technical error messages containing sensitive system information instead of suppressing internal details. A valid low-privilege session is required, and the disclosure supports further attacks without directly altering data or service availability.
Summary
What happened
Sensitive information disclosure in IBM Sterling Control Center 6.2.1 and 6.3.1 allows remote authenticated users to read browser error details. The web interface returns detailed technical error messages containing sensitive system information instead of suppressing internal details. A valid low-privilege session is required, and the disclosure supports further attacks without directly altering data or service availability.
The record
- CVE
- CVE-2024-35111
- Published
- Jan 25, 2025
- Updated
- Jan 27, 2025
- Vendor
- IBM
- Product
- IBM Sterling Control Center
- Classifications
- CWE-209
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 25, 2025CVE publishedPublication date reported by the CVE source.
- Jan 27, 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.1, 6.3.1
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