CVE-2017-18300
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 · uneditedSecure display content could be accessed by third party trusted application after creating a fault in other trusted applications in Snapdragon Mobile, Snapdragon Wear in version MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835, SDA660.
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 · moderate confidenceA vulnerability in Qualcomm Snapdragon chipsets allows a third-party trusted application to access secure display content by creating a fault in other trusted applications. This appears to be a flaw in the trusted execution environment (TEE) or secure display subsystem that can be exploited through a fault injection attack.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/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 the Qualcomm chipset modelCheck the device specifications or use system information commands (e.g., `cat /proc/cpuinfo` on Android, or check BIOS/UEFI information) to determine the exact Qualcomm Snapdragon or MDM chipset modelAffected if The chipset model is one of: Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 835, or Sda660
-
Determine the firmware versionQuery the TEE or secure display subsystem firmware version through manufacturer-specific diagnostic tools, or check the baseband processor firmware version using AT commands (e.g., `AT+QVER`), or access through Qualcomm's diagnostic interfaces if availableAffected if The firmware version cannot be determined or is an unpatched build
-
Check for OEM security updatesContact the device OEM or check the device manufacturer support website for security patch levels related to the TEE or secure display componentAffected if The device OEM has not released a security firmware update addressing this CVE
-
Verify TEE statusInspect the trusted execution environment status through debug interfaces or manufacturer diagnostic tools that query TEE integrity and versionAffected if The TEE firmware is present and running without documented patches for CVE-2017-18300
A user is affected if their device contains one of the listed Qualcomm chipset models and the TEE/secure display firmware has not been updated with Qualcomm's patch for this vulnerability.
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 security firmware updates provided by device OEMs that incorporate Qualcomm's patch for this vulnerability. Users should check with their device manufacturers for available updates.
- Consultation8.0 h
- Implementation4.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,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18300 — 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-2017-18300 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