dbcve.org
AndroidOperating system · Google

CVE-2022-20445

HIGH · 7.5 CVSS v3.1 Published 2022-11-08
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
In process_service_search_rsp of sdp_discovery.cc, there is a possible out of bounds read due to improper input validation. 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-225876506

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 confidence

This is an out-of-bounds read vulnerability in the Android Bluetooth stack's Service Discovery Protocol (SDP) implementation. The function process_service_search_rsp in sdp_discovery.cc fails to properly validate input bounds before reading data, allowing a remote attacker to read beyond allocated memory boundaries and disclose sensitive information from device memory via Bluetooth without any user interaction or elevated privileges.

MitigationApply the latest Android security patches (2022-12-01 or later) to affected devices. Organizations should ensure Bluetooth is disabled in sensitive environments until patches are applied, and maintain inventory of Android devices for patch management.

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
AndroidOperating system
Affected:= 10.0= 11.0= 12.0= 12.1= 13.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The version is 10.0, 11.0, 12.0, 12.1, or 13.0 exactly as listed in the affected versions
  2. Verify Bluetooth is enabled
    Check Settings > Bluetooth > On/Off toggle, or run 'settings get global bluetooth_on' via ADB
    Affected if Bluetooth is turned ON - the vulnerability exists in the SDP implementation and requires Bluetooth to be active for exploitation
  3. Check Android security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB
    Affected if The patch level is earlier than 2022-12-01 - devices without the December 2022 security update remain vulnerable

A device is affected if it runs Android 10.0, 11.0, 12.0, 12.1, or 13.0 with Bluetooth enabled and has a security patch level before December 2022.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest Android security patches (2022-12-01 or later) to affected devices. Organizations should ensure Bluetooth is disabled in sensitive environments until patches are applied, and maintain inventory of Android devices for patch management.

Recommended fix High confidence

Android devices with December 2022 security patch level (2022-12-05) or later; specifically Android 10, 11, 12, 12L, or 13 with latest security updates

  1. 1. Navigate to Settings on the Android device
  2. 2. Tap on 'System' or 'About phone'
  3. 3. Tap on 'Security' or 'Security & privacy'
  4. 4. Tap on 'Security patch level' to check the current patch level
  5. 5. If the patch level is earlier than December 2022, initiate a system update by checking for updates
  6. 6. Download and install the latest available Android security update containing the December 2022 patch or later
  7. 7. Restart the device after the update completes
Caveat Standard Android security update; no breaking changes expected for normal functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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