Adjacent-network information disclosure via risky cryptography
Published Dec 1, 2023 · Updated Sep 16, 2024
Information disclosure in IBM Planning Analytics on Cloud Pak for Data 4.0 allows remote attackers to read sensitive data over a shared network. IBM identifies insecure network communication and a risky cryptographic algorithm, but does not disclose the affected protocol, cryptographic primitive, or data exposed. Exploitation requires adjacent network access, needs no authentication or user interaction, and affects confidentiality without reported modification or interruption.
Summary
What happened
Information disclosure in IBM Planning Analytics on Cloud Pak for Data 4.0 allows remote attackers to read sensitive data over a shared network. IBM identifies insecure network communication and a risky cryptographic algorithm, but does not disclose the affected protocol, cryptographic primitive, or data exposed. Exploitation requires adjacent network access, needs no authentication or user interaction, and affects confidentiality without reported modification or interruption.
The record
- CVE
- CVE-2023-26024
- Published
- Dec 1, 2023
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Planning Analytics
- Classifications
- CWE-327, T1040
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 1, 2023CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=4.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