CVE-2020-11605
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 · uneditedAn issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) software. There is sensitive information exposure from dumpstate in NFC logs. The Samsung ID is SVE-2019-16359 (April 2020).
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 confidenceSamsung mobile devices running Android O (8.x), P (9.0), and Q (10.0) expose sensitive information through dumpstate functionality that writes NFC-related data to logs. This allows potentially sensitive NFC data to be accessible to authorized users or through diagnostic dumpstate files.
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.0= 8.1= 9.0= 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
- 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 device manufacturerRun 'getprop ro.product.brand' in ADB shell or check Settings > About Phone > Manufacturer. Confirm the device is a Samsung product.Affected if Device is not manufactured by Samsung - this vulnerability is specific to Samsung mobile devices.
-
Check Android versionRun 'getprop ro.build.version.release' in ADB shell or check Settings > About Phone > Android version. Verify the version is 8.0, 8.1, 9.0, or 10.0.Affected if Android version is outside the affected range (8.0-10.0). Versions 11 and later are not listed as affected.
-
Verify Samsung security patch levelRun 'getprop ro.build.version.security_patch' in ADB shell or check Settings > About Phone > Security patch level. Compare against the date of Samsung security update SVE-2019-16359.Affected if The security patch level predates the SVE-2019-16359 fix, meaning the vulnerability has not been patched by Samsung.
-
Inspect dumpstate output for NFC data exposureGenerate a bug report (dumpstate) via 'adb bugreport' or *#9900# and search the resulting ZIP/JSON files for NFC-related keywords (e.g., 'nfc', 'NFC', 'SE', 'secure element').Affected if NFC-related sensitive data appears in plain text within dumpstate output, indicating the unpatched behavior is present.
A Samsung device running Android 8.0, 8.1, 9.0, or 10.0 that has not received the Samsung security patch SVE-2019-16359 is affected by this NFC data exposure in dumpstate.
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 Samsung security patch (SVE-2019-16359) via OTA update or enterprise mobility management. This is a vendor-supplied fix; no user-level workarounds exist.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11605 — 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-2020-11605 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