CVE-2022-20447
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 PAN_WriteBuf of pan_api.cc, there is a possible out of bounds read due to a use after free. This could lead to remote information disclosure over Bluetooth with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-233604485
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 confidenceA use-after-free vulnerability in the PAN (Personal Area Network) Bluetooth component (pan_api.cc) allows an attacker to trigger an out-of-bounds read, potentially leaking sensitive information. The flaw is exploitable remotely via Bluetooth without requiring any user interaction or 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= 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.
-
Check Android versionNavigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The device is running Android 13.0 (exact version match)
-
Verify Bluetooth is enabledCheck Settings > Bluetooth to confirm Bluetooth is turned on, or run 'settings get global bluetooth_on' via ADB (returns 1 if enabled)Affected if Bluetooth is currently enabled on an Android 13.0 device
-
Confirm PAN service presenceRun 'dumpsys bluetooth_manager' or 'dumpsys connectivity' via ADB to check for PAN (Personal Area Network) service statusAffected if The PAN Bluetooth service is running or available on an Android 13.0 device with Bluetooth enabled
A device is affected if it runs Android 13.0 with Bluetooth and the PAN service enabled, as the use-after-free vulnerability exists in the PAN Bluetooth component.
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 Android security patch that addresses CVE-2022-20447 (December 2022 or later). As a defense-in-depth measure, users can disable Bluetooth when not in use to reduce attack surface, though this is not a substitute for patching.
Android 13 with 2022-10-05 security patch level or later monthly update
- Check current Android version and security patch level on the affected device via Settings > About Phone > Android version and Build number
- Ensure the device is connected to a network with Wi-Fi or mobile data
- Navigate to Settings > System > System Update > Check for Updates
- Download and install any available system updates
- After installation, verify the security patch level is 2022-10-05 or later via Settings > About Phone > Android version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.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 $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20447 — 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-20447 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