Skip to content
Fencer Intel
critical 9.8

CVE-2017-1000044 json

gtk-vnc 0.4.2 and older doesn't check framebuffer boundaries correctly when updating framebuffer which may lead to memory corruption when r…

published 2017-07-13 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-1369

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

Summary

gtk-vnc 0.4.2 and older doesn't check framebuffer boundaries correctly when updating framebuffer which may lead to memory corruption when rendering

Patch / fix

  • gtk-vnc Debian 14, Debian 13, Debian 12 0.4.3-1

debian advisories DEBIAN-CVE-2017-1000044

Vendor advisories

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

red hat product security vex CVE-2017-1000044 updated cvss 7.5

gtk-vnc: Incorrect boundaries check when updating framebuffer

  • Red Hat Enterprise Linux 5 gtk-vnc Red Hat Enterprise Linux 6 gtk-vnc, gtk-vnc-python
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 gvnc, gtk-vnc, gtk-vnc2, gvncpulse, gvnc-tools, gtk-vnc-python Red Hat Enterprise Virtualization 3 mingw-virt-viewer, mingw32-virt-viewer, mingw64-virt-viewer
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.