Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1410166 - (CVE-2016-9941) CVE-2016-9941 libvncserver: Heap-based buffer overflow in rfbproto.c
CVE-2016-9941 libvncserver: Heap-based buffer overflow in rfbproto.c
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20161114,repor...
: Security
Depends On: 1410180 1410178 1410179
Blocks: 1410176
  Show dependency treegraph
 
Reported: 2017-01-04 11:13 EST by Adam Mariš
Modified: 2017-05-25 23:54 EDT (History)
5 users (show)

See Also:
Fixed In Version: libvncserver 0.9.11
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-24 01:02:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2017-01-04 11:13:25 EST
Heap-based buffer overflow in rfbproto.c was found in LibVNCClient in LibVNCServer before 0.9.11 that allows remote servers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted FramebufferUpdate message containing a subrectangle outside of the client drawing area.

Upstream patch:

https://github.com/LibVNC/libvncserver/commit/5418e8007c248bf9668d22a8c1fa9528149b69f2

Upstream bug:

https://github.com/LibVNC/libvncserver/pull/137
Comment 1 Adam Mariš 2017-01-04 11:41:17 EST
Created libvncserver tracking bugs for this issue:

Affects: fedora-all [bug 1410178]
Affects: epel-5 [bug 1410179]
Affects: epel-7 [bug 1410180]
Comment 3 Fedora Update System 2017-05-25 23:54:49 EDT
libvncserver-0.9.11-2.fc24.1 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.