gtk-vnc 0.4.2 and older doesn't check framebuffer boundaries correctly when updating framebuffer which may lead to memory corruption when rendering
References
Link | Resource |
---|---|
https://git.gnome.org/browse/gtk-vnc/commit/?id=f3fc5e57a78d4be9872f1394f697b9929873a737 | Patch Vendor Advisory |
https://git.gnome.org/browse/gtk-vnc/commit/?id=f3fc5e57a78d4be9872f1394f697b9929873a737 | Patch Vendor Advisory |
Configurations
History
21 Nov 2024, 03:04
Type | Values Removed | Values Added |
---|---|---|
References | () https://git.gnome.org/browse/gtk-vnc/commit/?id=f3fc5e57a78d4be9872f1394f697b9929873a737 - Patch, Vendor Advisory |
Information
Published : 2017-07-17 13:18
Updated : 2024-11-21 03:04
NVD link : CVE-2017-1000044
Mitre link : CVE-2017-1000044
CVE.ORG link : CVE-2017-1000044
JSON object : View
Products Affected
gnome
- gtk-vnc
CWE
CWE-119
Improper Restriction of Operations within the Bounds of a Memory Buffer