CVE-2022-21844
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 · uneditedHEVC 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 confidenceCVE-2022-21844 is a Remote Code Execution vulnerability in the Windows HEVC Video Extensions codec. The vulnerability can be triggered when processing a specially crafted HEVC/H.265 video file, potentially allowing an attacker to execute arbitrary code with the privileges of the calling application.
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< 1.0.41532.0< 1.0.43421.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify HEVC Video Extensions is installedOpen PowerShell and run: Get-AppxPackage -Name Microsoft.HEVCVideoExtensionAffected if The package is not returned or not found in the list
-
Retrieve the installed version numberIn the same PowerShell output, locate the Version field for the Microsoft.HEVCVideoExtension packageAffected if The displayed version is lower than 1.0.41532.0 or 1.0.43421.0 (note: different build branches may use different minimum fixed versions)
-
Compare against affected version rangesDocument the exact version number and compare against the known vulnerable ranges: versions below 1.0.41532.0 and versions below 1.0.43421.0Affected if Your installed version falls below either of these threshold values
You are affected if the Microsoft.HEVCVideoExtension package is installed with a version number lower than 1.0.41532.0 or lower than 1.0.43421.0 (depending on your Windows build branch).
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.41532.01.0.43421.0
Apply the relevant Windows security update for HEVC Video Extensions via Windows Update, or ensure systems are on the current patch level.
HEVC Video Extensions version 1.0.43421.0 or later
- Open the Microsoft Store application on the Windows device
- Search for "HEVC Video Extensions" in the Store search bar
- Click on the HEVC Video Extensions app from the search results
- If an update is available, click the "Update" button to install the latest version
- Alternatively, open Windows Settings > Apps > Apps & features
- Locate "HEVC Video Extensions" in the list of installed apps
- Click on it and select "Update" if an update option is available
- Verify the installed version matches or exceeds 1.0.43421.0
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21844 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-21844 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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