Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1525195 - (CVE-2017-15124) CVE-2017-15124 Qemu: memory exhaustion through framebuffer update request message in VNC server
CVE-2017-15124 Qemu: memory exhaustion through framebuffer update request mes...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20171218,reported=2...
: Security
Depends On: 1527385 1526238 1526239 1526240 1526247 1526248 1526249 1527386 1527401 1527403 1527404 1527405 1527406 1527407 1527408 1527409
Blocks: 1525198
  Show dependency treegraph
 
Reported: 2017-12-12 13:24 EST by Pedro Sampaio
Modified: 2018-10-30 03:28 EDT (History)
42 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
VNC server implementation in Quick Emulator (QEMU) was found to be vulnerable to an unbounded memory allocation issue, as it did not throttle the framebuffer updates sent to its client. If the client did not consume these updates, VNC server allocates growing memory to hold onto this data. A malicious remote VNC client could use this flaw to cause DoS to the server host.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0816 None None None 2018-04-10 04:24 EDT
Red Hat Product Errata RHSA-2018:1104 None None None 2018-04-10 14:59 EDT
Red Hat Product Errata RHSA-2018:1113 None None None 2018-04-11 14:05 EDT
Red Hat Product Errata RHSA-2018:3062 None None None 2018-10-30 03:28 EDT

  None (edit)
Description Pedro Sampaio 2017-12-12 13:24:58 EST
VNC server implementation in Quick Emulator(QEMU) was found to be vulnerable to an unbounded memory allocation issue, as it did not throttle the framebuffer updates sent to its client. If the client did not consume these updates, VNC server allocates growing memory to hold onto this data.

A malicious VNC client could use this flaw to cause DoS on the remote server host.

Upstream fix(es):
-----------------
  -> https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg03715.html
  -> https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg03713.html
  -> https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg03711.html

Thread:
-------
  -> https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg03705.html

Reference:
----------
  -> http://www.openwall.com/lists/oss-security/2017/12/19/4
Comment 1 Pedro Sampaio 2017-12-12 13:25:14 EST
Acknowledgments:

Name: Daniel Berrange (Red Hat)
Comment 5 Prasad J Pandit 2017-12-19 05:35:50 EST
Created qemu tracking bugs for this issue:

Affects: fedora-all [bug 1527386]


Created xen tracking bugs for this issue:

Affects: fedora-all [bug 1527385]
Comment 15 errata-xmlrpc 2018-04-10 04:24:32 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2018:0816 https://access.redhat.com/errata/RHSA-2018:0816
Comment 16 errata-xmlrpc 2018-04-10 14:59:36 EDT
This issue has been addressed in the following products:

  Red Hat Virtualization 4 for RHEL-7

Via RHSA-2018:1104 https://access.redhat.com/errata/RHSA-2018:1104
Comment 17 errata-xmlrpc 2018-04-11 14:04:56 EDT
This issue has been addressed in the following products:

  Red Hat OpenStack Platform 10.0 (Newton)
  Red Hat OpenStack Platform 11.0 (Ocata)
  Red Hat OpenStack Platform 8.0 (Liberty)
  Red Hat OpenStack Platform 9.0 (Mitaka)
  Red Hat OpenStack Platform 12.0 (Pike)

Via RHSA-2018:1113 https://access.redhat.com/errata/RHSA-2018:1113
Comment 18 errata-xmlrpc 2018-10-30 03:28:10 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2018:3062 https://access.redhat.com/errata/RHSA-2018:3062

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