Local privilege escalation through undisclosed protection failure
Published Feb 16, 2023 · Updated Jan 27, 2025
Protection mechanism failure in Intel Media SDK before 22.2.2 allows local users to escalate privileges through local access. Intel has not published the affected component or the operation that fails to enforce the protection mechanism. Exploitation requires an authenticated local user and interaction by another user; the disclosed result is privilege escalation.
Summary
What happened
Protection mechanism failure in Intel Media SDK before 22.2.2 allows local users to escalate privileges through local access. Intel has not published the affected component or the operation that fails to enforce the protection mechanism. Exploitation requires an authenticated local user and interaction by another user; the disclosed result is privilege escalation.
The record
- CVE
- CVE-2022-27170
- Published
- Feb 16, 2023
- Updated
- Jan 27, 2025
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel Media SDK
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 16, 2023CVE publishedPublication date reported by the CVE source.
- Jan 27, 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=before version 22.2.2
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