CVE-2022-22074
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 during wma file playback due to integer overflow 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 confidenceMemory corruption vulnerability in Qualcomm Snapdragon chipsets during WMA file playback caused by an integer overflow. Specially crafted WMA files can trigger the overflow, leading to memory corruption and potential arbitrary code execution.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset model in your deviceCheck your device specifications, system information, or firmware documentation to determine the exact Qualcomm APQ chipset model (e.g., Apq8009, Apq8017, Apq8053, etc.)Affected if The chipset model matches one of the affected variants: Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Ar8035
-
Locate the firmware version for the Qualcomm chipsetAccess the device firmware settings, bootloader information, or system diagnostics to retrieve the installed firmware version for the identified Qualcomm chipsetAffected if The firmware version is present (all versions of the affected chipsets are listed as vulnerable)
-
Determine if WMA audio playback is enabledCheck the device audio configuration, media player settings, or codec list to see if Windows Media Audio (WMA) decoding/playback functionality is active for the chipsetAffected if WMA playback functionality is enabled and the device can process WMA audio files
-
Verify the device processes WMA media filesInspect media handling configurations or test with a WMA file to confirm the device will attempt to decode WMA content through the affected chipset componentAffected if The device has the capability to process WMA files through the vulnerable chipset component
You are affected if your device uses one of the listed Qualcomm chipset models (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, Ar8035) with any firmware version and has WMA playback functionality enabled that processes WMA files.
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 Qualcomm-provided security patches for affected Snapdragon components; device manufacturers should integrate firmware updates. Until patched, avoid processing WMA files from untrusted sources.
- Consultation16.0 h
- Implementation24.0 h
- Testing40.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $25,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22074 — 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-22074 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