dbcve.org
Roku FirmwareHardware / appliance · Roku

CVE-2018-11314

CRITICAL · 9.6 CVSS v3.0 Published 2018-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
The External Control API in Roku and Roku TV products allow unauthorized access via a DNS Rebind attack. This can result in remote device control and privileged device and network information to be exfiltrated by an attacker.

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 confidence

The External Control API in Roku and Roku TV devices lacks protection against DNS rebinding attacks, allowing attackers to bypass same-origin policy by controlling DNS responses to first resolve to an external domain then to the device's internal IP. This enables unauthorized remote control of the device and exfiltration of privileged network and device information.

MitigationImplement DNS rebinding protection at the network level (e.g., DNS firewall, protected DNS resolver) or through network segmentation to isolate Roku devices; ultimately requires vendor firmware update to add proper authentication and Host header validation to the API.

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
Roku FirmwareHardware / appliance
Affected:all versions

CVSS 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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify network exposure of Roku External Control API
    Scan your local network for devices listening on TCP port 8060 (the default Roku External Control API port). Use a command like 'nmap -p 8060 <your-network-range>' or check your router's device list and test port connectivity.
    Affected if A Roku device is found with TCP port 8060 open and responding to HTTP requests on your local network.
  2. Verify device responds to External Control API commands
    Send a benign HTTP request to the suspected Roku device at http://<device-ip>:8060/query/device-info and check for a valid JSON response containing device information.
    Affected if The device returns valid JSON/XML device information without any authentication, indicating the API is active and unprotected.
  3. Check if device is accessible from untrusted networks
    Test if the Roku's IP address is reachable from a network segment that should not have access (e.g., a guest WiFi network or from outside your NAT). Attempt to access http://<device-ip>:8060/query/device-info from an untrusted network segment.
    Affected if The External Control API is reachable from network segments that should be isolated from your main network.
  4. Assess network-level DNS rebinding protection
    Review your router or DNS resolver settings to determine if DNS rebinding protection is enabled. Check for settings like 'DNS rebinding protection', 'Bogus DNS responses', or similar security features that block private IP resolution from external DNS.
    Affected if Your network lacks DNS rebinding protection at the router or DNS resolver level, allowing external domains to resolve to internal IP addresses.

Your environment is affected if a Roku device with the External Control API (port 8060) is network-accessible and your network lacks DNS rebinding protection at the router or DNS resolver level.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement DNS rebinding protection at the network level (e.g., DNS firewall, protected DNS resolver) or through network segmentation to isolate Roku devices; ultimately requires vendor firmware update to add proper authentication and Host header validation to the API.

Fix this in Roku Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-11314 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-11314 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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