CVE-2019-5699
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 Shield TV Experience prior to v8.0.1, NVIDIA Tegra bootloader contains a vulnerability where the software performs an incorrect bounds check, which may lead to buffer overflow resulting in escalation of privileges and code execution. escalation of privileges, and information disclosure, code execution, denial of service, or escalation of privileges.
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 buffer overflow vulnerability exists in the NVIDIA Tegra bootloader due to an incorrect bounds check. This flaw allows an attacker to potentially overwrite memory beyond allocated buffers, leading to privilege escalation, arbitrary code execution, information disclosure, or denial of service on affected NVIDIA Shield TV devices running firmware versions prior to v8.0.1.
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.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 NVIDIA Shield TV modelLocate the model number on the device or retail packaging. Common models include SHIELD TV (2015), SHIELD TV (2017), and SHIELD TV Pro (2019).Affected if The device is any NVIDIA Shield TV model.
-
Check the Shield Experience versionOn the Shield TV, navigate to Settings > Device > About > Shield Experience. Alternatively, go to Settings > About > Version. Record the displayed version number.Affected if The displayed version number is lower than 8.0.1.
-
Verify the bootloader version (optional)Connect to the device via ADB (Android Debug Bridge) if developer options are enabled, then run 'adb shell getprop ro.bootloader' or 'adb shell getprop ro.build.version.preview_sdk' to retrieve bootloader-related properties.Affected if The bootloader version corresponds to a build prior to the 8.0.1 release.
-
Cross-reference with release notesCheck NVIDIA's official support pages or release notes for the 8.0.1 update to confirm the bootloader fix was included in that release.Affected if The installed version predates the 8.0.1 patch release date.
If the Shield Experience version is below 8.0.1, the device is running the vulnerable bootloader and is affected by this CVE.
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 data8.0.1
Update NVIDIA Shield TV Experience to version 8.0.1 or later to obtain the patched bootloader with proper bounds checking. If immediate patching is not possible, minimize the device's attack surface by restricting network access and avoiding untrusted input sources.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5699 — 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-5699 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