dbcve.org
Apq8017 FirmwareOperating system · Qualcomm

CVE-2022-22059

HIGH · 7.8 CVSS v3.1 Published 2022-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Memory corruption due to out of bound read while parsing a video file in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile

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

Out-of-bounds memory read vulnerability in video file parsing functionality within Qualcomm Snapdragon chipset firmware. The vulnerability allows memory corruption through specially crafted video files, potentially enabling information disclosure or code execution.

MitigationApply vendor-supplied firmware patches from Qualcomm and subsequent OEM updates for affected Snapdragon devices. Until patches are available, avoid parsing untrusted video 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 data
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Msm8917 FirmwareOperating system
Affected:all versions
Msm8953 FirmwareOperating system
Affected:all versions
Qca6390 FirmwareOperating system
Affected:all versions
Qca6391 FirmwareOperating system
Affected:all versions
Qca6420 FirmwareOperating system
Affected:all versions

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Identify the Qualcomm chipset model
    On Android: check /proc/cpuinfo or Settings > About Phone > Model/Hardware. On Linux embedded: check /proc/cpuinfo or run 'lspci' for network cards, or 'cat /sys/devices/soc0/soc_id' for Snapdragon SoC identification.
    Affected if The chipset model matches one of the affected models: Apq8017, Apq8053, Aqt1000, Msm8917, Msm8953, Qca6390, Qca6391, or Qca6420.
  2. Check the firmware version
    For mobile devices: check Settings > About Phone > Baseband version or Kernel version. For Qca WiFi chipsets: check via 'iw list' or 'wl -v' driver utilities, or check the firmware file version in /lib/firmware/qca/ on the host system.
    Affected if The firmware version is present and corresponds to an affected chipset (all versions of the listed chipsets are affected per the advisory).
  3. Determine if video parsing components are active
    On Android: check if video player apps are installed and have been used. Check running processes for media-related services (mediaserver, mediadrmserver, vendor.qti.media). For Qca chipsets in access points/routers: check if video streaming or multicast features are enabled in the firmware configuration.
    Affected if The device has video file parsing, video streaming, or multimedia processing functionality enabled and accessible.
  4. Check for vendor security updates
    For Android devices: check Settings > Security > Security patch level. For embedded devices: check the Qualcomm or OEM vendor security advisory pages for your specific model.
    Affected if The installed security patch level is earlier than the date when vendor patches for CVE-2022-22059 were released (vendor-specific dates vary).

The environment is potentially affected if it uses any of the listed Qualcomm chipset models (Apq8017, Apq8053, Aqt1000, Msm8917, Msm8953, Qca6390, Qca6391, Qca6420) and has not received vendor firmware updates that address this out-of-bounds read vulnerability in video parsing.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patches from Qualcomm and subsequent OEM updates for affected Snapdragon devices. Until patches are available, avoid parsing untrusted video files.

Fix this in Apq8017 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-22059 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