CVE-2022-27170

Protection mechanism failure in the Intel(R) Media SDK software before version 22.2.2 may allow an authenticated user to potentially enable escalation of privilege via local access.

Published: 2023-02-16 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-27170 is rated Low Risk (28.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.25%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-27170

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.05% 0.25% +0.19%
2 2026-03-09 0.19% 0.05% -0.13%
3 2026-02-25 — 0.19% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-27170

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.5 3.7 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2022-27170

OS Trackers for CVE-2022-27170

vendor priority summary link
debian end-of-life CVE-2022-27170 end-of-life priority: Debian including 1 source packages (intel-mediasdk), 2 status rows across 2 suites (bookworm, bullseye): open 1, resolved 1. https://security-tracker.debian.org/tracker/CVE-2022-27170
ubuntu medium CVE-2022-27170 medium priority: Ubuntu including 1 source packages (intel-mediasdk), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): not-affected 3, DNE 2, needed 1, released 1. https://ubuntu.com/security/CVE-2022-27170

Affected software / configurations for CVE-2022-27170

Vendor Product Version Raw CPE
intel media_software_development_kit < 22.2.2 cpe:2.3:a:intel:media_software_development_kit:*:*:*:*:*:*:*:*

References for CVE-2022-27170

cvelogic Threat Intelligence