CVE-2022-22087
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 · uneditedmemory corruption in video due to buffer overflow while parsing mkv clip with no codechecker in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
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 confidenceA buffer overflow vulnerability exists in the video parsing component when processing MKV (Matroska) video files. The parser fails to perform proper bounds checking during clip parsing, leading to memory corruption. This can potentially allow remote code execution or denial of service through specially crafted MKV files.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify the Qualcomm chipset model in the deviceCheck the processor/chipset information via /proc/cpuinfo, or check the device specifications/datasheet. Look for model numbers: Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620.Affected if The device uses any of the listed Qualcomm chipset models (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620)
-
Confirm the firmware version of the chipsetQuery the baseband or modem firmware version via AT commands (for modems) or through system information utilities. For Android devices, check via *#*#4636#*#* or settings > about phone > baseband version.Affected if Any firmware version is installed on an affected chipset - note that ALL versions of these chipsets are vulnerable, so the presence of the chipset itself is the key indicator
-
Verify if video parsing processing is enabledCheck device settings or system services related to video playback, video thumbnail generation, or video preview features. Look for services like mediaserver, videoeditor, or camera video processing modules.Affected if Video parsing or MKV processing functionality is enabled or installed on the device
-
Check for presence of video processing componentsInspect running processes and loaded libraries related to video handling. On Linux/Android systems, check /proc/<pid>/maps or look for libstagefright, libcodec, or similar video parsing libraries.Affected if Video parsing libraries or services that handle MKV container format are present and active on the system
The environment is affected if the system uses any of the vulnerable Qualcomm chipsets (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620) and has video/MKV processing capabilities enabled, since all firmware versions of these chipsets are vulnerable.
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.
From vendor dataApply vendor-supplied firmware/security patches from Qualcomm for affected Snapdragon chipsets. Until patches are available, restrict video file processing to trusted sources and disable automatic video preview features.
- Consultation12.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22087 — 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-22087 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