CVE-2019-8260
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 · uneditedUltraVNC revision 1199 has a out-of-bounds read vulnerability in VNC client RRE decoder code, caused by multiplication overflow. This attack appears to be exploitable via network connectivity. This vulnerability has been fixed in revision 1200.
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 confidenceUltraVNC revision 1199 contains an out-of-bounds read vulnerability in the VNC client RRE (Rectangle Encoding) decoder, caused by an integer multiplication overflow. The flaw is exploitable remotely via network connectivity and can lead to memory corruption or 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 data< 1.2.2.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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.
-
Identify installed UltraVNC versionOpen Windows Control Panel > Programs and Features, or right-click the UltraVNC icon and select 'About UltraVNC' to view the installed version number.Affected if The version displayed is earlier than 1.2.2.3 (or revision earlier than 1200)
-
Confirm UltraVNC client mode is in useVerify that UltraVNC is being used to connect to a remote VNC server (as opposed to only running as a VNC server/listener). The vulnerability exists in the RRE decoder which processes data received from remote servers.Affected if UltraVNC is configured or commonly used as a VNC client connecting to remote servers
-
Check UltraVNC revision numberIn the UltraVNC 'About' window, look for the revision number (build number). The vulnerable version is revision 1199 or earlier.Affected if The revision number shown is 1199 or lower
-
Identify RRE encoding usageWhen connecting to a VNC server, UltraVNC negotiates encoding types with the server. RRE (Rectangle Run-Length Encoding) is one of the supported encodings. Check connection logs or settings to confirm RRE encoding may be used for remote connections.Affected if RRE encoding is allowed or enabled in the connection settings, and connections are made to remote VNC servers
You are affected if UltraVNC version is earlier than 1.2.2.3 (revision below 1200) and the software is used as a VNC client to connect to remote servers using RRE encoding.
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.
dbcve · scoped1.2.2.3
Upgrade UltraVNC to revision 1200 or later to patch the multiplication overflow vulnerability in the RRE decoder.
UltraVNC 1.2.2.3 or later (contains revision 1200 fix)
- Download UltraVNC version 1.2.2.3 or later from the official UltraVNC website or a trusted source
- Verify the download using checksums if available
- Close any running UltraVNC instances
- Install the new version following the standard installation process
- Restart UltraVNC services if applicable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8260 — 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-8260 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