Sensitive information disclosure via body query parameters
Published May 14, 2021 · Updated Sep 16, 2024
Information disclosure in IBM Planning Analytics Local 2.0 allows remote attackers to obtain sensitive information through a crafted query. The Spreadsheet Services component accepts request-body parameters during query processing, but IBM has not disclosed the endpoint, parameter, or faulty data-selection logic. No authentication or user interaction is required, although IBM has not disclosed the condition that makes exploitation complex; only data disclosure is reported.
Summary
What happened
Information disclosure in IBM Planning Analytics Local 2.0 allows remote attackers to obtain sensitive information through a crafted query. The Spreadsheet Services component accepts request-body parameters during query processing, but IBM has not disclosed the endpoint, parameter, or faulty data-selection logic. No authentication or user interaction is required, although IBM has not disclosed the condition that makes exploitation complex; only data disclosure is reported.
The record
- CVE
- CVE-2020-4985
- Published
- May 14, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Planning Analytics Local
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2021CVE 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=2.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
No sourced classifications are available.
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