CVE-2021-0596
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 phNciNfc_RecvMfResp of phNxpExtns_MifareStd.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disclosure over NFC with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-8.1 Android-9 Android-10Android ID: A-181346550
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 phNciNfc_RecvMfResp function within the Android NFC Mifare Standard library (phNxpExtns_MifareStd.cpp). The function processes NFC tag responses without proper bounds validation, allowing an attacker within NFC range to read memory contents beyond intended buffer boundaries. This results in remote information disclosure with no user interaction or elevated privileges required.
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= 8.1= 9.0= 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
- 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 (or System > About Phone) and check the Android version field. Alternatively, run `getprop ro.build.version.release` via ADB or terminal.Affected if The version is 8.1, 9.0, 10.0, or 11.0 - these are the affected versions listed for this CVE.
-
Confirm NFC is enabledCheck Settings > Network & Internet > NFC (or Settings > Connections > NFC) to see if NFC is turned on. Alternatively, run `settings get global nfc_on` via ADB.Affected if NFC is turned on - the vulnerable code path in the Mifare Standard library is only reached when NFC is active and processing tag responses.
-
Check security patch levelGo to Settings > About Phone > Android version and look for the Security patch level date. Alternatively, run `getprop ro.build.version.security_patch` via ADB.Affected if The security patch level predates the fix for CVE-2021-0596 - the vulnerability was addressed in a later Android security bulletin after the affected versions were released.
-
Verify NFC tag reading capabilityAttempt to read an NFC tag (such as an ISO14443B or Mifare Classic tag) using an NFC-aware app or the device's built-in tag reader if available.Affected if The device successfully reads NFC tags - this confirms the Mifare Standard library (phNxpExtns_MifareStd.cpp) is actively processing responses, which is where the out-of-bounds read occurs.
A device is affected if it runs Android 8.1, 9.0, 10.0, or 11.0, has NFC enabled, and has not received the Android security update that patches CVE-2021-0596.
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.
From vendor dataApply the Android security patch for CVE-2021-0596 (available in Google's monthly security bulletins). The fix requires adding appropriate bounds checking in the phNciNfc_RecvMfResp function within the NFC stack. Users should ensure NFC is disabled when not in use and apply system updates promptly.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0596 — 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-2021-0596 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