dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2022-25669

HIGH · 7.5 CVSS v3.1 Published 2022-09-16
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 in video due to buffer over read while parsing MP4 clip 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

A buffer over-read vulnerability exists in the video parsing component when processing MP4 clips on Snapdragon chipset-based devices. This allows an attacker to trigger a denial of service by providing a specially crafted MP4 file that causes the buffer over-read during parsing.

MitigationApply the vendor-supplied firmware/security patch from Qualcomm for the affected Snapdragon product lines. Users should update their device firmware when patches become available through OEM/carrier channels.

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
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
Csra6640 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 the Qualcomm chipset model
    Check the device or system information to determine if the chipset is one of the following: Apq8009, Apq8009w, Apq8053, Apq8096au, Aqt1000, Ar8031, Csra6620, or Csra6640. On Android devices, this can be found in Settings > About Phone > Model/Hardware info, or via terminal command: 'getprop ro.board.platform' or 'getprop ro.product.device'. Check /proc/cpuinfo on embedded devices.
    Affected if The chipset model matches any of the affected APQ variants listed (Apq8009, Apq8009w, Apq8053, Apq8096au, Aqt1000, Ar8031, Csra6620, Csra6640)
  2. Verify the firmware version
    Query the firmware version on the device. On Android: 'getprop ro.build.version.security_patch' or check Settings > About Phone > Android security patch level. On embedded systems, check the firmware version via: 'cat /etc/version' or the relevant bootloader/firmware version command.
    Affected if The device runs any firmware version on the affected chipset models, since all versions are vulnerable
  3. Confirm video/MP4 parsing is enabled
    Determine if the device has video playback capability and whether apps or services can process MP4 files. Check if media frameworks (such as MediaCodec, Stagefright on Android, or similar on embedded systems) are present and active. Look for video player applications or services that process MP4 content.
    Affected if The device has video playback capability and can parse MP4 files through its media subsystem
  4. Assess MP4 file processing exposure
    Evaluate whether the device processes MP4 files from untrusted sources. Check if third-party apps can load MP4 files, if the device can receive MP4 files via messaging/email, or if it plays MP4 from external/untrusted sources like web downloads or messaging apps.
    Affected if The device can process MP4 files from untrusted or external sources without strict validation

A user is affected if their device contains a Qualcomm Apq8009, Apq8009w, Apq8053, Apq8096au, Aqt1000, Ar8031, Csra6620, or Csra6640 chipset and has the ability to parse MP4 video files, since all firmware versions of these chipsets contain the vulnerability.

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 the vendor-supplied firmware/security patch from Qualcomm for the affected Snapdragon product lines. Users should update their device firmware when patches become available through OEM/carrier channels.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,960
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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