CVE-2022-20483
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 · uneditedIn several functions that parse avrc response in avrc_pars_ct.cc and related files, there are possible out of bounds reads due to integer overflows. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12L Android-13Android ID: A-242459126
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 · high confidenceInteger overflows in AVRCP (Audio/Video Remote Control Protocol) response parsing functions in avrc_pars_ct.cc allow out-of-bounds memory reads. By sending crafted Bluetooth AVRCP responses, a remote attacker can read adjacent heap memory contents without authentication or user interaction.
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= 10.0= 11.0= 12.0= 12.1= 13.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Check Android versionGo to Settings > About Phone > Android version and note the displayed version numberAffected if The version is exactly 10.0, 11.0, 12.0, 12.1, or 13.0
-
Check Security Patch LevelGo to Settings > About Phone > Security patch level and note the dateAffected if The security patch level is earlier than 2022-12-05
-
Confirm Bluetooth is in useThis vulnerability affects the AVRCP protocol parser in the Bluetooth stack; if the device has Bluetooth capability and runs any of the affected Android versions, the vulnerable code is present regardless of current Bluetooth on/off stateAffected if Device runs an affected Android version with Bluetooth stack enabled
Device is affected if it runs Android 10.0, 11.0, 12.0, 12.1, or 13.0 and has a Security Patch Level earlier than 2022-12-05, as the integer overflow vulnerability in the AVRCP response parser exists in the Bluetooth framework of those versions.
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.
dbcve · scopedApply Android security patch level 2022-12-05 or later. This is a platform-level vulnerability requiring a system update from Google or the device OEM; no user-side configuration can mitigate it.
Android-13 (or any Android version with December 2022 security patch level or later)
- Check current Android version and security patch level in Settings > About Phone > Android version
- Navigate to Settings > System > Security update to verify if December 2022 or later security patch is installed
- If not updated, check for system software updates: Settings > System > Software Update
- Download and install the latest available system update containing the December 2022 security patch or later
- After update, verify the security patch level shows December 2022 or later in Settings > About Phone > Android version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,712.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20483 — 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-20483 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