dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2022-33266

HIGH · 7.8 CVSS v3.1 Published 2023-01-09
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 in Audio due to integer overflow to buffer overflow while music playback of clips like amr,evrc,qcelp with modified content.

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 the Audio component stemming from an integer overflow that leads to a buffer overflow condition. The vulnerability is triggered during music playback of specifically crafted audio clips in AMR, EVRC, or QCELP formats with modified content, allowing potential arbitrary code execution.

MitigationApply vendor-provided security patches for the Audio component; avoid playing untrusted or modified audio files until the update is deployed.

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
Apq8064au FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Ar8035 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 in your device
    Check the device specifications, system information, or boot logs for the chipset identifier (Apq8009, Apq8009w, Apq8017, Apq8064au, Apq8096au, Aqt1000, Ar8031, or Ar8035)
    Affected if The device uses any of the listed affected chipset models (Apq8009, Apq8009w, Apq8017, Apq8064au, Apq8096au, Aqt1000, Ar8031, Ar8035)
  2. Check the firmware version
    Retrieve the firmware version from the device settings, about phone page, or via AT commands (for modems): at+ver, at+cgmr, or through /proc/version on Linux-based embedded systems
    Affected if The firmware version matches any of the affected products listed in the CVE (all versions of the listed chipsets are affected)
  3. Verify if AMR audio codec support is enabled
    Check system settings, audio codec configuration files, or audio driver modules for AMR (Adaptive Multi-Rate) codec availability. On Android, check /system/etc/audio_policy.conf or investigate audio.ext*.so libraries
    Affected if AMR audio playback capability is present and enabled on the device
  4. Verify if EVRC audio codec support is enabled
    Inspect the audio configuration or codec libraries for EVRC (Enhanced Variable Rate Codec) support. Check /proc/asound/cards, audio HAL dumps, or vendor audio configuration files
    Affected if EVRC audio playback capability is present and enabled on the device
  5. Verify if QCELP audio codec support is enabled
    Examine audio codec settings, vendor-specific audio libraries, or modem audio configuration for QCELP (Qualcomm Code Excited Linear Prediction) codec support
    Affected if QCELP audio playback capability is present and enabled on the device

The device is affected if it contains any of the listed Qualcomm chipsets (Apq8009, Apq8009w, Apq8017, Apq8064au, Apq8096au, Aqt1000, Ar8031, Ar8035) and has AMR, EVRC, or QCELP audio playback enabled, as all firmware versions of these chipsets are vulnerable.

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-provided security patches for the Audio component; avoid playing untrusted or modified audio files until the update is deployed.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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