Skip to content
Fencer Intel
critical 9.8

CVE-2019-8273 json

UltraVNC revision 1211 has a heap buffer overflow vulnerability in VNC server code inside file transfer request handler, which can potentia…

published 7y ago modified 4mo ago also EUVD-2019-17671

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.3%
EPSS 8.3% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

UltraVNC revision 1211 has a heap buffer overflow vulnerability in VNC server code inside file transfer request handler, which can potentially result in code execution. This attack appears to be exploitable via network connectivity. This vulnerability has been fixed in revision 1212.

Patch / fix

  • uvnc ultravnc 1.2.2.3
  • siemens sinumerik_access_mymachine/p2p 4.8
  • siemens sinumerik_pcu_base_win10_software/ipc 14.00

Is CVE-2019-8273 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-20-161-06 updated cvss 9.8

Siemens SINUMERIK

  • Siemens SINUMERIK Access MyMachine /P2P <V4.8
    affected: fixed in V4.8, mitigation
  • Siemens SINUMERIK PCU base Win7 software /IPC <V12.01_HF4
    affected: fixed in V12.01, mitigation
  • Siemens SINUMERIK PCU base Win10 software /IPC <V14.00
    affected: fixed in V14.00, mitigation

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Exploit prediction

8.26% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Kaspersky Lab UltraVNC

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.