CVE-2022-20468
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 BNEP_ConnectResp of bnep_api.cc, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information disclosure over Bluetooth 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-228450451
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 confidenceAn out-of-bounds read vulnerability exists in the BNEP (Bluetooth Network Encapsulation Protocol) stack within the BNEP_ConnectResp function in bnep_api.cc. The vulnerability stems from an incorrect bounds check that allows reading memory beyond intended buffer boundaries, potentially exposing sensitive information from kernel or userspace memory over Bluetooth.
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= 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/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.
-
Identify the Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is 10.0, 11.0, 12.0, or 13.0
-
Check the Android security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if Security patch level is earlier than December 2022 (the fix release date)
-
Verify Bluetooth BNEP/PAN functionality is activeCheck if Bluetooth is enabled and a Personal Area Network (PAN) connection is active - look for tethering or hotspot usage over Bluetooth, or check 'bnep' kernel module statusAffected if Bluetooth is enabled and BNEP (Bluetooth Network Encapsulation Protocol) is in active use for PAN connections
You are affected if your device runs Android 10, 11, 12, or 13 with a security patch level earlier than December 2022 and you use Bluetooth PAN networking with BNEP enabled.
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 security patch released by Google for this CVE through the standard Android system update mechanism. Users should ensure their devices receive the latest Android security update.
December 2022 Android Security Bulletin (Android Security Patch Level 2022-12-01) or later for Android 10, 11, 12, 12L, and 13
- Navigate to Settings > Security on the Android device
- Check for and install the latest Android system updates
- Ensure the device receives the December 2022 Android Security Bulletin patch or later (Android Security Patch Level 2022-12-01 or higher)
- Verify the update was applied by checking Settings > About Phone > Android version to confirm the Security Patch Level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20468 — 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-20468 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