CVE-2022-20131
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 nci_proc_rf_management_ntf of nci_hrcv.cc, there is a possible out of bounds read due to a missing bounds check. 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-12LAndroid ID: A-221856662
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 missing bounds check in the nci_proc_rf_management_ntf function of nci_hrcv.cc (part of Android's NFC Controller Interface stack) allows an out-of-bounds read. This enables remote information disclosure via NFC proximity without requiring user interaction or additional 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.0= 12.0= 12.1CVSS 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.
-
Identify Android versionGo to Settings > About Phone > Android version (or run 'getprop ro.build.version.release' via ADB)Affected if The version displayed is 10.0, 11.0, 12.0, or 12.1
-
Confirm NFC capability existsCheck if the device has NFC hardware by looking for NFC in Settings > Connected Devices > NFC (or check 'getprop ro.hardware.nfc' via ADB)Affected if The device has NFC hardware present
-
Verify NFC is enabledNavigate to Settings > Connected Devices > NFC and check if the toggle is ON, or run 'nfc check' via ADB if availableAffected if NFC is currently enabled on the device
A device is affected if it runs Android 10.0, 11.0, 12.0, or 12.1 AND has NFC hardware that is currently enabled, allowing a remote out-of-bounds read via NFC proximity without user interaction.
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 relevant Android security patch (2022-07-01 or later) to address the bounds check vulnerability in the NFC NCI processing code. Until patched, limit exposure by disabling NFC when not in use.
Upgrade to the latest available Android security patch (July 2022 or later) or migrate to a newer Android version with ongoing support
- Check the current Android version and security patch level on the device in Settings > About Phone > Android version
- Apply the latest Android security update by going to Settings > System > Security Update and installing any available updates
- If the device is on Android-12L and no longer receiving security updates, upgrade to a newer Android version or consider更换设备 to receive ongoing security patches
- Verify the security patch level has been updated to include the July 2022 security patch or later which addresses CVE-2022-20131
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20131 — 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-20131 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