CVE-2023-22666
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 in Audio while playing amrwbplus clips 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 confidenceMemory corruption vulnerability in the audio playback subsystem when processing AMR-WB+ audio files with modified content. The vulnerability is triggered by specially crafted/malformed audio clips that cause memory corruption during parsing or decoding of the AMR-WB+ format.
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 modelCheck system information via 'cat /proc/cpuinfo' or 'dmesg | grep -i qualcomm' to determine the exact chipset (Apq8009, Apq8017, Apq8096au, Aqt1000, Ar8031, Ar8035, Csra6620, or Csra6640)Affected if The chipset matches any of the eight affected models (Apq8009, Apq8017, Apq8096au, Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640)
-
Verify AMR-WB+ audio codec supportCheck if the AMR-WB+ decoder is loaded or available on the system - look for audio codec modules via 'ls /lib/modules/$(uname -r)/kernel/sound/' or check /proc/asound/codecs for codec presenceAffected if The AMR-WB+ codec is loaded or listed as available in the audio subsystem
-
Check audio firmware versionExamine audio processor firmware version if accessible - commands like 'cat /sys/firmware/devicetree/base/model' or checking /proc/bootinfo may reveal firmware version detailsAffected if The firmware version cannot be determined or is earlier than any vendor patch date (no patches have been publicly released for this CVE based on provided data)
-
Identify AMR-WB+ audio file processing capabilityDetermine if any application on the system can process AMR-WB+ audio files - check for AMR-WB+ support in media players or audio libraries via 'ffmpeg -codecs 2>/dev/null | grep -i amr' or similar audio toolAffected if The system has capability to decode or play AMR-WB+ audio files from any source
You are affected if your device uses any of the eight listed Qualcomm chipsets AND has AMR-WB+ audio playback capability enabled, since all firmware versions of these chipsets are vulnerable and the flaw triggers during AMR-WB+ file processing.
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 vendor patches for the affected audio component; avoid playing AMR-WB+ audio files from untrusted or unknown sources until the patch is applied.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22666 — 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-2023-22666 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