CVE-2022-20023
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 Bluetooth, there is a possible application crash due to bluetooth flooding a device with LMP_AU_rand packet. This could lead to remote denial of service of bluetooth with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06198608; Issue ID: ALPS06198608.
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 confidenceThis is a Bluetooth stack vulnerability where an attacker can flood a target device with specially crafted LMP_AU_rand (Link Manager Protocol Authentication Random) packets, causing a remote denial of service crash of the Bluetooth subsystem. The attack is remote, requires no user interaction, and needs no elevated privileges.
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.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Android versionGo to Settings > About Phone and check the Android version. Alternatively, run 'adb shell getprop ro.build.version.release'Affected if The version is 10.0 or 11.0 exactly (not 10.0.x or 11.0.x with additional point releases)
-
Confirm Bluetooth is enabledCheck if Bluetooth is turned on in Settings > Bluetooth, or run 'adb shell settings get global bluetooth_on' (returns 1 if enabled)Affected if Bluetooth is enabled and discoverable - the device must have Bluetooth active to receive the malicious LMP_AU_rand packets
-
Check security patch levelGo to Settings > About Phone > Security Patch Level, or run 'adb shell getprop ro.build.version.security_patch'Affected if The patch level is earlier than the vendor fix (ALPS06198608) - if the date is before the fix release date, the vulnerability is likely unpatched
You are affected if your device runs Android 10.0 or 11.0, has Bluetooth enabled, and lacks the vendor security patch that fixes the LMP_AU_rand packet handling flaw.
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 the vendor patch (ALPS06198608) which fixes the Bluetooth stack handling of LMP_AU_rand packets. Until the patch is available, limit Bluetooth device exposure to trusted devices and networks.
Android Security Patch Level March 2022 or later (contact device manufacturer for specific firmware version)
- Check the current Android security patch level on the device in Settings > About Phone > Android security patch level
- Ensure the device has Android Security Bulletin from March 2022 or later applied
- Apply any available system updates from the device manufacturer that include the March 2022 security patch level
- Verify after update that the security patch level is March 2022 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20023 — 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-20023 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