CVE-2017-6287
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 libnvrm contains a possible out of bounds read due to a missing bounds check which could lead to local information disclosure. This issue is rated as moderate.Product: Android. Version: N/A. Android: A-64893264. Reference: N-CVE-2017-6287.
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 libnvrm library on Android contains an out-of-bounds read vulnerability caused by a missing bounds check. An attacker with local access could exploit this to read sensitive information from memory beyond allocated buffers. The vulnerability does not provide code execution, only information disclosure.
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 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.
-
Locate the libnvrm library on the Android deviceSearch for libnvrm.so in common system library directories: ls /system/lib/libnvrm.so ls /vendor/lib/libnvrm.so ls /system/vendor/lib/libnvrm.soAffected if The library file exists on the device, indicating the NVIDIA libnvrm component is present
-
Verify the library is a shared object from NVIDIARun 'file' on the discovered library if found: file /system/lib/libnvrm.soAffected if The file is identified as a shared object (ELF) from NVIDIA, confirming the affected component is installed
-
Check if the library is loaded by running processesUse 'ps -A | grep' or check /proc/*/maps to see if any process has libnvrm.so mapped into memory, or examine APK manifests for native library referencesAffected if The library is loaded into memory by any application or system service, making the vulnerable code path potentially reachable
-
Confirm Android OEM patch statusCheck system security patch level in Settings > About Phone > Android Security Patch Level, or run 'getprop ro.build.version.security_patch'Affected if The security patch level is earlier than the vendor fix date for CVE-2017-6287 (Android A-64893264), indicating the vulnerability may remain unpatched
A device is affected if the NVIDIA libnvrm library is present and the Android security patch level does not include the CVE-2017-6287 fix.
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 vendor patch for CVE-2017-6287 (Android A-64893264) to the affected NVIDIA libnvrm library. Users should update their Android devices and verify that OEM-specific patches have been applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6287 — 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-6287 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