CVE-2019-9383
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 NFC server, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-120843827
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 confidenceIn the Android 10 NFC server component, an out-of-bounds read vulnerability exists due to a missing bounds check. This allows a local attacker to read sensitive information without elevated privileges, but requires user interaction (likely involving NFC functionality) to trigger the exploit.
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.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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.
-
Confirm Android version is 10.0Check Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Android version shows exactly 10.0 (not 9, 8, 11, or later)
-
Verify NFC is enabledCheck Settings > Network & Internet > NFC (or Settings > Connections > NFC on Samsung devices), or run 'nfc list' or check NFC service status via 'dumpsys nfc'Affected if NFC is turned ON in device settings
-
Determine if NFC host card emulation or beam is in useCheck for apps using HCE (Host Card Emulation) or review recent NFC beam/tab activities in system logs, or check if NFC is configured for payment/transfer functionsAffected if NFC is configured for active use cases (payments, tag reading, HCE, or file transfer)
-
Check installed Android security patch levelRun 'getprop ro.build.version.security_patch' via ADB shell or check Settings > About Phone > Android security patch levelAffected if Security patch level is earlier than the patch that addresses CVE-2019-9383 (typically November 2019 or earlier for Android 10)
Device is affected if it runs Android 10.0 with NFC enabled and has a security patch level earlier than the fix for CVE-2019-9383.
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-2019-9383 (typically included in Android 10 monthly security updates); this is a platform-level vulnerability that cannot be remediated through application-level fixes and requires updating the device firmware/OS.
- Consultation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9383 — 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-2019-9383 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