Privilege escalation via unquoted service path
Published Mar 12, 2020 · Updated Aug 4, 2024
Unquoted service path handling in Intel ipmctl before 1.0.0.3461 allows local users to elevate privileges and interrupt its service. A Windows service registration leaves an executable path containing spaces unquoted, so service startup can resolve an attacker-controlled executable earlier in that path. Exploitation requires authenticated local access and write access to a searched parent directory; Intel has not identified the affected service or path.
Summary
What happened
Unquoted service path handling in Intel ipmctl before 1.0.0.3461 allows local users to elevate privileges and interrupt its service. A Windows service registration leaves an executable path containing spaces unquoted, so service startup can resolve an attacker-controlled executable earlier in that path. Exploitation requires authenticated local access and write access to a searched parent directory; Intel has not identified the affected service or path.
The record
- CVE
- CVE-2020-0546
- Published
- Mar 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Intel
- Product
- Intel ipmctl
- Classifications
- CWE-428, T1574.009
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=before version 1.0.0.3461
- Affected versionversion=See advisory https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00326.html
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