CVE-2019-16110
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 · uneditedThe network protocol of Blade Shadow though 2.13.3 allows remote attackers to take control of a Shadow instance and execute arbitrary code by only knowing the victim's IP address, because packet data can be injected into the unencrypted UDP packet stream.
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 · high confidenceBlade Shadow cloud gaming client through version 2.13.3 uses an unencrypted UDP-based network protocol. Remote attackers can inject malicious packets into the UDP stream using only the victim's IP address, enabling full remote code execution and control of the Shadow instance.
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<= 2.13.3CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 if Blade Shadow client is installedLook for Blade Shadow application in the system's installed programs list. On Windows, check Add/Remove Programs or the installation directory (typically C:\Program Files\Blade\Shadow or similar). On Mac, check /Applications for Shadow app.Affected if Blade Shadow client is found on the system
-
Determine the installed version numberOpen the Blade Shadow application and navigate to Help > About, or right-click the application in the installed programs list to view version details. Compare the version to 2.13.3.Affected if The installed version is 2.13.3 or lower
-
Verify the UDP-based service is activeWhile Blade Shadow is running, use netstat or a network monitoring tool to observe UDP traffic on ports commonly used by Shadow (check application documentation or observe active connections).Affected if The application is running and actively using UDP connections for network communication
-
Check network exposureDetermine if the system has a public IP address or is directly exposed to the internet (check router WAN IP, firewall rules allowing UDP inbound). The vulnerability is exploitable remotely if the system is reachable via UDP.Affected if The system has direct inbound UDP accessibility from untrusted networks
A user is affected if Blade Shadow client version 2.13.3 or lower is installed and actively using unencrypted UDP communication on a network accessible to remote attackers.
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 dataImplement encrypted transport (DTLS or similar UDP-compatible encryption) for the network protocol; apply vendor patches when available; consider network segmentation to limit exposure.
- Consultation8.0 h
- Implementation40.0 h
- Testing20.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $21,184.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16110 — 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-16110 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