CVE-2019-8287
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 · uneditedTightVNC code version 1.3.10 contains global buffer overflow in HandleCoRREBBP macro function, which can potentially result code execution. This attack appear to be exploitable via network connectivity.
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 confidenceTightVNC 1.3.10 contains a global buffer overflow in the HandleCoRREBBP macro function. This macro handles a specific RFB protocol message type, and the overflow occurs when processing malformed or oversized data, allowing an attacker to overwrite memory and potentially execute arbitrary code remotely.
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= 1.3.10CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Verify TightVNC installation and versionCheck the installed version of TightVNC. On Windows, open Control Panel > Programs and Features, or run 'wmic product get name,version' or check the TightVNC service properties. On Linux, check with 'vncserver -version' or check package management.Affected if The installed version is exactly 1.3.10.
-
Confirm TightVNC server service is runningCheck if the TightVNC server service (tvnserver or TightVNC Server) is running. On Windows, open Services and look for 'TightVNC Server' or run 'sc query tvnserver'. On Linux, check with 'ps aux | grep vnc' or 'systemctl status tvnserver'.Affected if The service is running and the version is 1.3.10.
-
Check if TightVNC is listening on network portsVerify TightVNC is bound to network interfaces. Run 'netstat -an | findstr 5900' or 'netstat -an | findstr 5901' on Windows, or 'netstat -tlnp | grep vnc' on Linux. This shows if the VNC server is listening on TCP ports.Affected if TightVNC is listening on network interfaces (0.0.0.0 or external IP) and the version is 1.3.10.
-
Inspect TightVNC configuration for remote access settingsLocate and review the TightVNC configuration file (tvnserver.ini on Windows, ~/.vnc/config on Linux). Check for 'AllowLoopback' or 'AllowRemoteConnections' settings that enable remote connections.Affected if Remote connections are enabled in the config and the version is 1.3.10.
A user is affected if TightVNC version 1.3.10 is installed, the server service is running, and it is configured to accept remote network connections on TCP ports 5900+.
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 dataUpgrade TightVNC to the latest version or apply the vendor patch. If immediate patching is not possible, disable or restrict network access to the TightVNC service and implement network segmentation.
- Consultation4.0 h
- Implementation6.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,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8287 — 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-8287 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