Hevc Video ExtensionsPlugin / extension · Microsoft

CVE-2022-22006

HIGH · 7.8 CVSS v3.1 Published 2022-03-09
Fix available
A fix is available. Upgrade to 1.0.50361.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HEVC Video Extensions Remote Code Execution Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a remote code execution vulnerability in Windows HEVC Video Extensions (the codec for H.265 video playback). An attacker can exploit this by persuading a user to open a specially crafted HEVC video file, leading to arbitrary code execution with the user's privileges. The vulnerability stems from improper memory handling in the video codec.

MitigationApply the Microsoft security updates for HEVC Video Extensions via Windows Update or deploy KB5012345 and subsequent patches through patch management. If HEVC extensions are not required, consider disabling them through Windows Features.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hevc Video ExtensionsPlugin / extension
Affected:< 1.0.50361.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify HEVC Video Extensions are installed
    Open PowerShell and run: Get-AppxPackage -Name Microsoft.HEVCVideoExtension* | Select-Object Name, Version
    Affected if The package is not found or no results returned means the extension is not installed and not affected
  2. Confirm the installed version number
    If the package is found, note the Version field from the output of the previous command
    Affected if Unable to retrieve a version number means the installation may be corrupted or non-standard
  3. Compare version against vulnerable range
    Compare the installed version to 1.0.50361.0 - versions lower than 1.0.50361.0 are vulnerable (e.g., 1.0.50242.0, 1.0.49006.0)
    Affected if Installed version is less than 1.0.50361.0 indicates the environment is vulnerable
  4. Check if HEVC video handling is active
    The vulnerability triggers when opening a specially crafted HEVC video file - no special configuration needs to be enabled beyond having the extension installed
    Affected if HEVC Video Extensions are installed with a vulnerable version and the user can open video files means the system is exploitable

User is affected if Microsoft HEVC Video Extensions are installed with a version lower than 1.0.50361.0, as the vulnerability triggers when processing HEVC video files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.50361.0 or later
Fixed in 1.0.50361.0
Interim mitigation

Apply the Microsoft security updates for HEVC Video Extensions via Windows Update or deploy KB5012345 and subsequent patches through patch management. If HEVC extensions are not required, consider disabling them through Windows Features.

Recommended fix High confidence

Version 1.0.50361.0 or later

  1. Open the Microsoft Store application on your Windows device
  2. Click on the Library icon (usually in the lower-left corner)
  3. Click 'Get updates' to check for available updates
  4. Locate 'HEVC Video Extensions' in the list of available updates
  5. Click 'Update' to install the latest version
  6. Alternatively, search for 'HEVC Video Extensions' in the Microsoft Store and click Update if an update is available
  7. Verify the installed version is 1.0.50361.0 or later via Windows Settings > Apps > HEVC Video Extensions > Version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hevc Video Extensions Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22006 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data