CVE-2017-15124: Input Validation

Published Dec 12, 2017
·
Updated

Last updated 25 August 2025

Other sources

VNC server implementation in Quick Emulator (QEMU) 2.11.0 and older 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.

Launchpad

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

Red Hat

Affected Software

2 affected componentsFixes available
Qemu Qemu<=2.11.0
debian/qemu
1:5.2+dfsg-11+deb11u31:5.2+dfsg-11+deb11u51:7.2+dfsg-7+deb12u181:7.2+dfsg-7+deb12u151:10.0.11+ds-0+deb13u11:10.0.2+ds-2+deb13u11:11.0.2+ds-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/qemu to a version that resolves this vulnerability.

    Fixed in 1:5.2+dfsg-11+deb11u3Fixed in 1:5.2+dfsg-11+deb11u5Fixed in 1:7.2+dfsg-7+deb12u18Fixed in 1:7.2+dfsg-7+deb12u15Fixed in 1:10.0.11+ds-0+deb13u1Fixed in 1:10.0.2+ds-2+deb13u1Fixed in 1:11.0.2+ds-2
  2. Upgrade

    Upgrade QEMU VNC server (Quick Emulator) to a version that resolves this vulnerability.

    Fixed in 2.11.0

Event History

Dec 12, 2017
Data Sourced
via Red Hat·06:24 PM
DescriptionSeverityAffected Software
Dec 19, 2017
Data Sourced
09:42 PM
SeverityAffected Software
Jan 9, 2018
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
DescriptionWeakness
Data Sourced
via NVD·09:29 PM
DescriptionSeverityWeaknessAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·10:31 PM
Description
Feb 19, 2026
Data Sourced
via Ubuntu·08:14 PM
RemedyDescriptionSeverityAffected Software
Jul 16, 2026
Data Sourced
via Debian·11:14 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-15124?

CVE-2017-15124 has been classified with a medium severity due to its potential for unbounded memory allocation.

2

How do I fix CVE-2017-15124?

To mitigate CVE-2017-15124, upgrade to QEMU versions higher than 2.11.0.

3

What software is affected by CVE-2017-15124?

CVE-2017-15124 affects QEMU versions 2.11.0 and older.

4

What are the consequences of not addressing CVE-2017-15124?

Failure to address CVE-2017-15124 may lead to denial of service due to excessive memory allocation.

5

Is CVE-2017-15124 applicable to all operating systems?

CVE-2017-15124 is primarily relevant for systems running affected versions of QEMU.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203