Privileged credential disclosure via OMI trace logging
Published Nov 14, 2023 · Updated Oct 8, 2025
Information disclosure in OMI 1.7.1-0 and earlier for Microsoft SCOM allows local users to read privileged-account credentials from trace logs. OMI writes privileged-account credentials into trace files instead of excluding sensitive authentication data from diagnostic logging. Exploitation requires an authenticated local user with permission to read a trace file on a Linux machine monitored by SCOM, and disclosure can compromise resources beyond the OMI security scope.
Summary
What happened
Information disclosure in OMI 1.7.1-0 and earlier for Microsoft SCOM allows local users to read privileged-account credentials from trace logs. OMI writes privileged-account credentials into trace files instead of excluding sensitive authentication data from diagnostic logging. Exploitation requires an authenticated local user with permission to read a trace file on a Linux machine monitored by SCOM, and disclosure can compromise resources beyond the OMI security scope.
The record
- CVE
- CVE-2023-36043
- Published
- Nov 14, 2023
- Updated
- Oct 8, 2025
- Vendor
- Microsoft
- Product
- Microsoft System Center Operations Manager 2022
- Classifications
- CWE-200, CWE-668, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 14, 2023CVE publishedPublication date reported by the CVE source.
- Oct 8, 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=10.22.0 <1.7.3-0
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