CVE-2018-11806: Qemu Slirp Networking Heap-based Buffer Overflow Privilege Escalation Vulnerability

Published Jun 5, 2018
·
Updated

A heap buffer overflow issue was found in the way Slirp networking back-end in QEMU processes fragmented packets. It could occur while reassembling the fragmented datagrams of an incoming packet.

A privileged user/process inside guest could use this flaw to crash the QEMU process resulting in DoS OR potentially leverage it to execute arbitrary code on the host with privileges of the QEMU process.

Upstream patch: --------------- -> https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg01012.html

Reference: ---------- -> http://www.openwall.com/lists/oss-security/2018/06/07/1

Other sources

mcat in slirp/mbuf.c in Qemu has a heap-based buffer overflow via incoming fragmented datagrams.

Launchpad

Affected Software

30 affected componentsFixes available
Qemu Qemu<=2.12.1
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=18.10
redhat Openstack=8
redhat Openstack=9
redhat Openstack=10
redhat Openstack=12
redhat Openstack=13
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Eus=7.5
redhat Enterprise Linux Eus=7.6
redhat Enterprise Linux Eus=7.7
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Aus=7.7
redhat Enterprise Linux Server Tus=7.6
redhat Enterprise Linux Server Tus=7.7
redhat Enterprise Linux Workstation=6.0
redhat Enterprise Linux Workstation=7.0
redhat Virtualization=4.0
redhat Enterprise Linux=7.0
Debian Debian Linux=8.0
Debian Debian Linux=9.0
All of the following
redhat Virtualization=4.0
redhat Enterprise Linux=7.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.8+ds-0+deb13u11:10.0.2+ds-2+deb13u11:11.0.0+ds-21:11.0.1+ds-1

Event History

Jun 5, 2018
Data Sourced
via Red Hat·07:58 PM
DescriptionSeverityAffected Software
Jun 13, 2018
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Data Sourced
via NVD·04:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·10:47 PM
Description
Feb 20, 2026
Data Sourced
via Ubuntu·03:57 PM
RemedyDescriptionSeverityAffected Software
Jun 1, 2026
Data Sourced
via Debian·05:09 PM
DescriptionAffected Software
Jun 11, 2026
Advisory Published
via ZDI·05:22 PM
Data Sourced
via ZDI·05:22 PM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2018-11806?

The severity of CVE-2018-11806 is high (8.2).

2

How can an attacker exploit CVE-2018-11806?

An attacker must first obtain the ability to execute code on the guest OS in order to exploit CVE-2018-11806.

3

Which software is affected by CVE-2018-11806?

Qemu versions 1:2.11+dfsg-1ubuntu7.8, 2.0.0+dfsg-2ubuntu1.44, and 1:2.5+dfsg-5ubuntu10.33 are affected by CVE-2018-11806.

4

How do I fix CVE-2018-11806?

To fix CVE-2018-11806, update Qemu to version 1:3.1+dfsg-8+deb10u8 or later if using Debian, or version 1:2.11+dfsg-1ubuntu7.8 or later if using Ubuntu.

5

Where can I find more information about CVE-2018-11806?

You can find more information about CVE-2018-11806 at the following references: [1](https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg01012.html), [2](http://www.openwall.com/lists/oss-security/2018/06/07/1), [3](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1586249).

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