Report disclosure and modification via identifier authorization bypass
Published Mar 18, 2024 · Updated Oct 10, 2024
Improper authorization in BMC Control-M 9.0.20 and 9.0.21 allows remote authenticated users to read and alter unauthorized reports. The report module accepts a user-controlled unique report identifier without enforcing the requester’s object permissions before reading or updating the report. A valid login and the exact report identifier are required; the resulting impact is limited to report confidentiality and integrity.
Summary
What happened
Improper authorization in BMC Control-M 9.0.20 and 9.0.21 allows remote authenticated users to read and alter unauthorized reports. The report module accepts a user-controlled unique report identifier without enforcing the requester’s object permissions before reading or updating the report. A valid login and the exact report identifier are required; the resulting impact is limited to report confidentiality and integrity.
The record
- CVE
- CVE-2024-1604
- Published
- Mar 18, 2024
- Updated
- Oct 10, 2024
- Vendor
- BMC Software, Inc.
- Product
- Control-M
- Classifications
- CWE-639, T1565.001, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 18, 2024CVE publishedPublication date reported by the CVE source.
- Oct 10, 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=9.0.20 <9.0.20.238
- Affected versionversion=9.0.21 <9.0.21.201
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.
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