Local privilege escalation via permissive installer defaults
Published Aug 14, 2024 · Updated Aug 14, 2024
Incorrect default permissions in Intel Connectivity Performance Suite installers before 2.0 allow local users to gain elevated privileges. Intel identifies installer default permissions as the locus but has not disclosed which object receives overly broad access or how it is modified. Exploitation requires low local privileges, high complexity, and active user interaction before installer execution can yield elevated access.
Summary
What happened
Incorrect default permissions in Intel Connectivity Performance Suite installers before 2.0 allow local users to gain elevated privileges. Intel identifies installer default permissions as the locus but has not disclosed which object receives overly broad access or how it is modified. Exploitation requires low local privileges, high complexity, and active user interaction before installer execution can yield elevated access.
The record
- CVE
- CVE-2023-43747
- Published
- Aug 14, 2024
- Updated
- Aug 14, 2024
- Vendor
- Intel Corporation
- Product
- Intel Connectivity Performance Suite
- Classifications
- CWE-276, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 14, 2024CVE publishedPublication date reported by the CVE source.
- Aug 14, 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=0 <2.0
- Affected versionversion=before version 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
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