dbcve.org
UltravncApplication · Uvnc

CVE-2019-8265

CRITICAL · 9.8 CVSS v3.0 Published 2019-03-08
Fix available
A fix is available. Upgrade to 1.2.2.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
UltraVNC revision 1207 has multiple out-of-bounds access vulnerabilities connected with improper usage of SETPIXELS macro in VNC client code, which can potentially result in code execution. This attack appears to be exploitable via network connectivity. These vulnerabilities have been fixed in revision 1208.

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 confidence

UltraVNC revision 1207 contains multiple out-of-bounds access vulnerabilities in the VNC client code due to improper usage of the SETPIXELS macro. These memory corruption flaws can be exploited remotely via network connectivity to achieve arbitrary code execution.

MitigationUpgrade UltraVNC from revision 1207 to revision 1208 or later to remediate the out-of-bounds access vulnerabilities in the SETPIXELS macro implementation.

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
UltravncApplication
Affected:< 1.2.2.3

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
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 checks

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

  1. Identify UltraVNC installation and version
    Open Windows Control Panel > Programs and Features, or right-click the UltraVNC icon in the system tray and select 'About UltraVNC'. Record the displayed version number.
    Affected if The installed version is below 1.2.2.3 (or revision 1207)
  2. Confirm UltraVNC client component is present
    Check for the presence of vncviewer.exe in the UltraVNC installation directory (typically C:\Program Files\UltraVNC or C:\Program Files (x86)\UltraVNC).
    Affected if The vncviewer.exe executable exists and is version 1.2.2.2 or lower
  3. Determine if UltraVNC Viewer is configured to accept incoming connections
    Open UltraVNC Viewer properties or check the listening mode configuration. Look for settings such as 'Listen on port' or 'Listening for incoming connections' in the Viewer UI or registry under HKLM\Software\UltraVNC or HKCU\Software\UltraVNC.
    Affected if Listening mode is enabled and the Viewer is configured to accept remote connections
  4. Compare installed version to affected range
    If the version cannot be determined via GUI, check the file properties of vncviewer.exe: right-click the file, select Properties, and review the 'File version' or 'Product version' field.
    Affected if The file version shows anything earlier than 1.2.2.3 (or the product version indicates revision 1207 or earlier)

The environment is affected if UltraVNC Viewer version 1.2.2.2 or earlier (revision 1207 or earlier) is installed and the client component is present with remote connectivity enabled.

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.

dbcve · scoped
Upgrade available Upgrade to 1.2.2.3 or later
Fixed in 1.2.2.3
Interim mitigation

Upgrade UltraVNC from revision 1207 to revision 1208 or later to remediate the out-of-bounds access vulnerabilities in the SETPIXELS macro implementation.

Recommended fix High confidence

1.2.2.3 or later (revision 1208)

  1. 1. Identify all systems running UltraVNC version 1.2.2.2 or earlier
  2. 2. Download UltraVNC version 1.2.2.3 or later from the official UltraVNC website or a trusted distribution source
  3. 3. Ensure any active VNC connections are terminated before upgrading
  4. 4. Run the installer for the new version with appropriate administrative privileges
  5. 5. Follow the installation prompts to complete the upgrade
  6. 6. Verify the installed version is 1.2.2.3 or later by checking Help > About in the UltraVNC viewer
  7. 7. Test VNC functionality to ensure the client and server operate correctly after the upgrade
  8. 8. Update any deployment mechanisms (e.g., SCCM, GPO, scripts) to deploy version 1.2.2.3 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ultravnc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-8265 — 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-2019-8265 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