dbcve.org
UltravncApplication · Uvnc

CVE-2019-8272

CRITICAL · 9.8 CVSS v3.1 Published 2019-03-08
Fix available
A fix is available. Upgrade to 1.2.2.3 / 4.8 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 1211 has multiple off-by-one vulnerabilities in VNC server code, which can potentially result in code execution. This attack appears to be exploitable via network connectivity. These vulnerabilities have been fixed in revision 1212.

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 1211 contains multiple off-by-one vulnerabilities in the VNC server code. These memory corruption vulnerabilities can be exploited remotely via network connectivity to achieve arbitrary code execution. The vulnerabilities were patched in revision 1212.

MitigationUpgrade UltraVNC to revision 1212 or later to remediate the off-by-one vulnerabilities in the VNC server component.

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
Sinumerik Access Mymachine\/p2pApplication
Affected:< 4.8
Sinumerik Pcu Base Win10 Software\/ipcApplication
Affected:< 14.00
Sinumerik Pcu Base Win7 Software\/ipcApplication
Affected:<= 12.01

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

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

  1. Identify if UltraVNC server is installed
    Check for UltraVNC server components on the system. Look for uvnc_service.exe, winvnc.exe, or similar VNC server executables in program directories or running processes.
    Affected if UltraVNC server component is present on the system
  2. Determine the installed UltraVNC version
    Right-click the UltraVNC server executable (such as winvnc.exe or uvnc_service.exe), select Properties, and check the File Version. Alternatively, check the version from Add/Remove Programs or the about dialog if accessible.
    Affected if The version is below 1.2.2.3 (or revision 1211) for standalone UltraVNC installations
  3. Identify Siemens Sinumerik software installations
    Check for Siemens Sinumerik-related software packages: Sinumerik Access Mymachine, Sinumerik Pcu Base Win10 Software, or Sinumerik Pcu Base Win7 Software. Look in Program Files or the Windows installed programs list.
    Affected if Any of these Siemens products are installed and contain bundled UltraVNC components
  4. Check Siemens product versions
    For each identified Siemens Sinumerik product, determine the version number. For Access Mymachine/p2p, check if version is below 4.8. For Pcu Base Win10 Software, check if below 14.00. For Pcu Base Win7 Software, check if version is 12.01 or below.
    Affected if The installed Siemens product version falls within the affected range
  5. Verify VNC server service is enabled or running
    Check if the UltraVNC server service (uvnc_service or winvnc) is running as a service or process. Open Services.msc and look for UltraVNC Server, or check Task Manager for winvnc.exe process.
    Affected if The VNC server service is installed and running, making the vulnerability reachable over the network

The system is affected if UltraVNC server (standalone or bundled with Siemens Sinumerik software) is installed with a version below 1.2.2.3 (or revision 1211) and the VNC server component is enabled or running.

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 / 4.8 / 14.00 or later
Fixed in 1.2.2.34.814.00
Interim mitigation

Upgrade UltraVNC to revision 1212 or later to remediate the off-by-one vulnerabilities in the VNC server component.

Recommended fix High confidence

UltraVNC revision 1212 or version 1.2.2.3 and later; Siemens Sinumerik products should update to vendor-specified fixed versions

  1. 1. Identify the currently installed UltraVNC version by checking the application or binary version information
  2. 2. Download UltraVNC revision 1212 or version 1.2.2.3 (or later) from the official UltraVNC repository or a trusted source
  3. 3. Back up the current UltraVNC configuration files if applicable
  4. 4. Upgrade UltraVNC to the fixed revision by running the installer of the fixed version
  5. 5. For Siemens Sinumerik products (Access Mymachine/p2p, Pcu Base Win7/Win10 Software/ipc), apply the vendor-supplied updates that include the patched UltraVNC component: Access Mymachine/p2p version 4.8 or later, Pcu Base Win10 Software/ipc version 14.00 or later, Pcu Base Win7 Software/ipc version 12.02 or later
  6. 6. Verify the installation and restart the VNC service if necessary

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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