dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2022-22083

HIGH · 7.5 CVSS v3.1 Published 2022-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Denial of service due to memory corruption while extracting ape header from clips 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 confidence

Memory corruption vulnerability in Qualcomm Snapdragon processors during APE audio format header extraction. The vulnerability allows attackers to trigger denial of service via specially crafted APE audio files that cause memory corruption in the media parsing subsystem.

MitigationApply Qualcomm firmware/security updates for affected Snapdragon chipset variants when available; avoid processing untrusted APE audio files from unknown sources until patches are applied.

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
Apq8009 FirmwareOperating system
Affected:all versions
Apq8009w FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Csra6620 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 your Snapdragon chipset model
    On Android devices, check /proc/cpuinfo for 'Hardware' or 'model name', or go to Settings > About Phone > Chipset/Processor info. On embedded devices, check the board documentation or BOM (Bill of Materials).
    Affected if The chipset model matches one of: Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620. If your device uses one of these specific Snapdragon variants, proceed to the next check.
  2. Verify the media subsystem is active
    Check if the device has active media processing capabilities. On Android, look for running media services (mediaserver, mediametrics) via 'ps -A | grep media' or check if audio playback apps are installed and functional.
    Affected if The media parsing subsystem is enabled and functional. Since APE audio parsing is part of standard media handling, this is typically always true on consumer devices with audio capabilities.
  3. Confirm all firmware versions are affected
    Review the CVE advisory: all versions of the listed firmware are vulnerable. There is no specific patched version number to compare against for these chipsets.
    Affected if Your device runs any firmware version on an affected chipset. The vulnerability exists across the entire version range for these specific Snapdragon models.
  4. Check for related crash logs
    Search device logs (logcat on Android, dmesg on Linux-based embedded systems) for crashes related to 'APE', 'audio', 'media', or 'memory corruption' around the time of audio file processing.
    Affected if You observe media subsystem crashes, memory corruption errors, or unexpected reboots when processing APE audio files, indicating potential exploitation.

You are affected if your device or embedded system uses any of the following Snapdragon chipset models: Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620, and the media subsystem processes audio files including APE format.

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 Qualcomm firmware/security updates for affected Snapdragon chipset variants when available; avoid processing untrusted APE audio files from unknown sources until patches are applied.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22083 — 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-22083 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