Authenticated performance-metrics disclosure via missing authorization
Published May 6, 2020 · Updated Sep 16, 2024
Incorrect authorization in IBM BPM 8.0, 8.5, and 8.6 and Business Automation Workflow 18.0 and 19.0 lets remote authenticated users read metrics. The performance-metrics display returns monitoring data without enforcing expected authorization checks. A low-privileged account and network access are required, and the documented impact is limited to metric confidentiality.
Summary
What happened
Incorrect authorization in IBM BPM 8.0, 8.5, and 8.6 and Business Automation Workflow 18.0 and 19.0 lets remote authenticated users read metrics. The performance-metrics display returns monitoring data without enforcing expected authorization checks. A low-privileged account and network access are required, and the documented impact is limited to metric confidentiality.
The record
- CVE
- CVE-2020-4446
- Published
- May 6, 2020
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- Business Automation Workflow
- Classifications
- CWE-863, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2020CVE 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=18.0.0.0
- Affected versionversion=19.0.0.1
What conditions does exploitation require?
What is affected?
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.
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