CVE-2017-6295
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 · uneditedNVIDIA TrustZone Software contains a vulnerability in the Keymaster implementation where the software reads data past the end, or before the beginning, of the intended buffer; and may lead to denial of service or information disclosure. This issue is rated as high.
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 confidenceNVIDIA TrustZone Software contains a buffer overread vulnerability in the Keymaster cryptographic key storage implementation. The flaw allows reading data beyond the intended buffer boundaries, potentially exposing sensitive key material or causing denial of service.
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<= 6.2all 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/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 NVIDIA Shield TV firmware versionCheck the firmware version on the NVIDIA Shield TV device through Settings > About > Version. Compare the version number to the affected range (<=6.2).Affected if The device is an NVIDIA Shield TV running firmware version 6.2 or lower
-
Verify NVIDIA TrustZone component presenceOn the affected device, inspect the TrustZone or Keymaster component information. This may be available through security settings, diagnostic tools, or by examining the /proc/ or /sys/ directories for keymaster-related entries.Affected if The device implements NVIDIA's TrustZone Keymaster and the version cannot be determined or is older than the patched release
-
Confirm Android Keymaster implementation vendorOn Android devices, determine which vendor provides the Keymaster implementation. This can typically be verified through keymaster HAL dumps, security reports, or by checking the keystore provider information.Affected if The device uses NVIDIA's Keymaster implementation (as opposed to other vendors like Qualcomm, ARM, or software-only implementations)
-
Check if Keymaster cryptographic operations are in useDetermine if the device actively uses Keymaster for cryptographic key storage. This is typically the default on devices with hardware-backed security. Verify through keystore status or security configuration settings.Affected if The device uses Keymaster for cryptographic operations and runs the affected NVIDIA software stack
A user is affected if they use an NVIDIA Shield TV with firmware 6.2 or earlier, or any Android device that utilizes NVIDIA's TrustZone Keymaster implementation for cryptographic key storage.
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 NVIDIA-provided firmware/security patches for TrustZone and Keymaster components. Verify Keymaster implementation through TrustZone certification or penetration testing if patches are unavailable.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6295 — 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-6295 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