CVE-2019-20610
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 N(7.X) and O(8.X) (Exynos 7570, 7870, 7880, 7885, 8890, 8895, and 9810 chipsets) software. A double-fetch vulnerability in Trustlet allows arbitrary TEE code execution. The Samsung ID is SVE-2019-13910 (April 2019).
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 double-fetch race condition vulnerability in the Trustlet component on Samsung devices with Exynos chipsets (7570, 7870, 7880, 7885, 8890, 8895, 9810) running Android N(7.X) and O(8.X) allows an attacker to manipulate memory values between two successive reads, enabling arbitrary Trusted Execution Environment (TEE) code execution with the highest privilege level.
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= 7.0= 7.1.0= 7.1.1= 7.1.2= 8.0= 8.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 the device manufacturerCheck if the device is a Samsung product by examining system properties or device information (Settings > About Phone > Manufacturer)Affected if Device is not manufactured by Samsung, the vulnerability does not apply
-
Identify the chipset modelCheck the processor/chipset information through device settings, system diagnostic tools, or by examining /proc/cpuinfo for the Exynos model numberAffected if Chipset is not one of: 7570, 7870, 7880, 7885, 8890, 8895, 9810
-
Check the Android OS versionCheck Settings > About Phone > Android version, or run 'getprop ro.build.version.release' in ADB shellAffected if Android version is 7.0, 7.1.0, 7.1.1, 7.1.2, 8.0, or 8.1 (exact match required)
-
Verify Trustlet component presenceCheck for the presence of Trustlet binary or TEE-related files in /vendor/firmware/ or /system/firmware/ directories (requires root or diagnostic access)Affected if Trustlet component exists on the device - the vulnerability applies to any Samsung Exynos device in the affected version range
The device is affected if it is a Samsung device with an Exynos 7570, 7870, 7880, 7885, 8890, 8895, or 9810 chipset running Android 7.0 through 8.1.
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 vendor-supplied firmware updates from Samsung; this is a TEE firmware vulnerability requiring a Trustlet patch that cannot be fixed through application-level code changes.
- Consultation8.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 $6,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20610 — 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-20610 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