CVE-2020-8608
published 2020-02-06CVE-2020-8608: In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overflow in later code.
PriorityP431medium5.6CVSS 3.1
AVNACHPRNUINSUCLILAL
EPSS
2.49%
82.8th percentile
In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overflow in later code.
Affected
25 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | libslirp | < libslirp 4.2.0-1 (bookworm) | libslirp 4.2.0-1 (bookworm) |
| debian | qemu | < libslirp 4.2.0-1 (bookworm) | libslirp 4.2.0-1 (bookworm) |
| debian | slirp | < libslirp 4.2.0-1 (bookworm) | libslirp 4.2.0-1 (bookworm) |
| debian | slirp4netns | < libslirp 4.2.0-1 (bookworm) | libslirp 4.2.0-1 (bookworm) |
| libslirp_project | libslirp | — | — |
| libslirp_project | libslirp | >= 0 < 4.2.0-1 | 4.2.0-1 |
| libslirp_project | libslirp | >= 0 < 4.2.0-1 | 4.2.0-1 |
| libslirp_project | libslirp | >= 0 < 4.2.0-1 | 4.2.0-1 |
| libslirp_project | libslirp | >= 0 < 4.2.0-1 | 4.2.0-1 |
| opensuse | leap | — | — |
| qemu | qemu | >= 0 < 1:4.1-2 | 1:4.1-2 |
| qemu | qemu | >= 0 < 1:4.1-2 | 1:4.1-2 |
| qemu | qemu | >= 0 < 1:4.1-2 | 1:4.1-2 |
| qemu | qemu | >= 0 < 1:4.1-2 | 1:4.1-2 |
| qemu | qemu | >= 0 < 1:2.5+dfsg-5ubuntu10.43 | 1:2.5+dfsg-5ubuntu10.43 |
| qemu | qemu | >= 0 < 1:2.11+dfsg-1ubuntu7.23 | 1:2.11+dfsg-1ubuntu7.23 |
| qemu | qemu | >= 0 < 1:4.2-3ubuntu6.30 | 1:4.2-3ubuntu6.30 |
| qemu | qemu | >= 0 < 1:6.2+dfsg-2ubuntu6.24 | 1:6.2+dfsg-2ubuntu6.24 |
| qemu | qemu | >= 0 < 1:8.2.2+ds-0ubuntu1.4 | 1:8.2.2+ds-0ubuntu1.4 |
| qemu | qemu | >= 0 < 2.0.0+dfsg-2ubuntu1.47+esm4 | 2.0.0+dfsg-2ubuntu1.47+esm4 |
| qemu | qemu | >= 0 < 1:2.5+dfsg-5ubuntu10.51+esm3 | 1:2.5+dfsg-5ubuntu10.51+esm3 |
| qemu | qemu | >= 0 < 1:2.11+dfsg-1ubuntu7.42+esm2 | 1:2.11+dfsg-1ubuntu7.42+esm2 |
CVSS provenance
nvdv3.15.6MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
osv6.0MEDIUM
vendor_ubuntu7.7HIGH
vendor_debian5.6MEDIUM
vendor_redhat5.6MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
qemu vulnerabilities
osv·2024-11-08·CVSS 3.5
CVE-2019-20382 [LOW] qemu vulnerabilities
qemu vulnerabilities
It was discovered that QEMU incorrectly handled memory during certain VNC
operations. A remote attacker could possibly use this issue to cause QEMU
to consume resources, resulting in a denial of service. This issue only
affected Ubuntu 14.04 LTS. (CVE-2019-20382)
It was discovered that QEMU incorrectly handled certain memory copy
operations when loading ROM contents. If a user were tricked into running
an untrusted kernel image, a remote attacker could possibly use this issue
to run arbitrary code. This issue only affected Ubuntu 14.04 LTS.
(CVE-2020-13765)
Aviv Sasson discovered that QEMU incorrectly handled Slirp networking. A
remote attacker could use this issue to cause QEMU to crash, resulting in a
denial of service, or possibly execute arbitrary code. This iss
GHSA
GHSA-495h-ww9w-vg4p: In libslirp 4
ghsa_unreviewed·2022-05-24
CVE-2020-8608 [HIGH] CWE-120 GHSA-495h-ww9w-vg4p: In libslirp 4
In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overflow in later code.
OSV
slirp vulnerabilities
osv·2020-11-12·CVSS 5.6
CVE-2020-7039 [MEDIUM] slirp vulnerabilities
slirp vulnerabilities
It was discovered that the SLiRP networking implementation of the QEMU
emulator did not properly manage memory under certain circumstances. An
attacker could use this to cause a heap-based buffer overflow or other out-
of-bounds access, which can lead to a denial of service (application crash)
or potentially execute arbitrary code. (CVE-2020-7039)
It was discovered that the SLiRP networking implementation of the QEMU
emulator misuses snprintf return values. An attacker could use this to
cause a denial of service (application crash) or potentially execute
arbitrary code. (CVE-2020-8608)
OSV
qemu vulnerabilities
osv·2020-02-18·CVSS 6.0
CVE-2020-1711 [MEDIUM] qemu vulnerabilities
qemu vulnerabilities
Felipe Franciosi, Raphael Norwitz, and Peter Turschmid discovered that QEMU
incorrectly handled iSCSI server responses. A remote attacker in control of
the iSCSI server could use this issue to cause QEMU to crash, leading to a
denial of service, or possibly execute arbitrary code. (CVE-2020-1711)
It was discovered that the QEMU libslirp component incorrectly handled
memory. A remote attacker could use this issue to cause QEMU to crash,
resulting in a denial of service, or possibly execute arbitrary code.
(CVE-2020-7039, CVE-2020-8608)
OSV
CVE-2020-8608: In libslirp 4
osv·2020-02-06·CVSS 5.6
CVE-2020-8608 [MEDIUM] CVE-2020-8608: In libslirp 4
In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overflow in later code.
Ubuntu
QEMU vulnerabilities
vendor_ubuntu·2024-11-08·CVSS 3.5
CVE-2020-8608 [LOW] QEMU vulnerabilities
Title: QEMU vulnerabilities
Summary: Several security issues were fixed in QEMU.
It was discovered that QEMU incorrectly handled memory during certain VNC
operations. A remote attacker could possibly use this issue to cause QEMU
to consume resources, resulting in a denial of service. This issue only
affected Ubuntu 14.04 LTS. (CVE-2019-20382)
It was discovered that QEMU incorrectly handled certain memory copy
operations when loading ROM contents. If a user were tricked into running
an untrusted kernel image, a remote attacker could possibly use this issue
to run arbitrary code. This issue only affected Ubuntu 14.04 LTS.
(CVE-2020-13765)
Aviv Sasson discovered that QEMU incorrectly handled Slirp networking. A
remote attacker could use this issue to cause QEMU to crash, resulting in a
de
Ubuntu
SLiRP vulnerabilities
vendor_ubuntu·2020-11-12·CVSS 5.6
CVE-2020-7039 [MEDIUM] SLiRP vulnerabilities
Title: SLiRP vulnerabilities
Summary: slirp could be made to crash if it received specially crafted
input.
It was discovered that the SLiRP networking implementation of the QEMU
emulator did not properly manage memory under certain circumstances. An
attacker could use this to cause a heap-based buffer overflow or other out-
of-bounds access, which can lead to a denial of service (application crash)
or potentially execute arbitrary code. (CVE-2020-7039)
It was discovered that the SLiRP networking implementation of the QEMU
emulator misuses snprintf return values. An attacker could use this to
cause a denial of service (application crash) or potentially execute
arbitrary code. (CVE-2020-8608)
Instructions: In general, a standard system update will make all the necessary changes.
Ubuntu
QEMU vulnerabilities
vendor_ubuntu·2020-02-18·CVSS 7.7
CVE-2020-1711 [HIGH] QEMU vulnerabilities
Title: QEMU vulnerabilities
Summary: Several security issues were fixed in QEMU.
Felipe Franciosi, Raphael Norwitz, and Peter Turschmid discovered that QEMU
incorrectly handled iSCSI server responses. A remote attacker in control of
the iSCSI server could use this issue to cause QEMU to crash, leading to a
denial of service, or possibly execute arbitrary code. (CVE-2020-1711)
It was discovered that the QEMU libslirp component incorrectly handled
memory. A remote attacker could use this issue to cause QEMU to crash,
resulting in a denial of service, or possibly execute arbitrary code.
(CVE-2020-7039, CVE-2020-8608)
Instructions: After a standard system update you need to restart all QEMU virtual
machines to make all the necessary changes.
Red Hat
QEMU: Slirp: potential OOB access due to unsafe snprintf() usages
vendor_redhat·2020-01-27·CVSS 5.6
CVE-2020-8608 [MEDIUM] CWE-122 QEMU: Slirp: potential OOB access due to unsafe snprintf() usages
QEMU: Slirp: potential OOB access due to unsafe snprintf() usages
In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overflow in later code.
An out-of-bounds heap buffer access flaw was found in the SLiRP networking implementation of the QEMU emulator. This flaw occurs in tcp_emu() routine while emulating IRC and other protocols due to unsafe usage of the snprintf(3) function. A user or process could use this flaw to crash the QEMU process on the host, resulting in a denial of service or potential execution of arbitrary code with privileges of the QEMU process on the host.
Statement: This issue affects user-mode or SLiRP networking implementation of the QEMU emulator. Though qemu-kvm package is built with SLiRP networking support, du
Debian
CVE-2020-8608: libslirp - In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return val...
vendor_debian·2020·CVSS 5.6
CVE-2020-8608 [MEDIUM] CVE-2020-8608: libslirp - In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return val...
In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overflow in later code.
Scope: local
bookworm: resolved (fixed in 4.2.0-1)
bullseye: resolved (fixed in 4.2.0-1)
forky: resolved (fixed in 4.2.0-1)
sid: resolved (fixed in 4.2.0-1)
trixie: resolved (fixed in 4.2.0-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-8608 webkitgtk: Multiple memory corruption issues leading to arbitrary code execution
bugzilla·2020-09-08·CVSS 6.3
CVE-2019-8608 [MEDIUM] CVE-2019-8608 webkitgtk: Multiple memory corruption issues leading to arbitrary code execution
CVE-2019-8608 webkitgtk: Multiple memory corruption issues leading to arbitrary code execution
WebKitGTK Security Advisory WSA-2019-0003 describes the following issue:
CVE-2019-8608
Processing maliciously crafted web content may lead to arbitrary code execution. Multiple memory corruption issues were addressed with improved memory handling.
Versions affected: WebKitGTK and WPE WebKit before 2.24.1.
Discussion:
External References:
https://webkitgtk.org/security/WSA-2019-0003.html
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 7
Via RHSA-2020:4035 https://access.redhat.com/errata/RHSA-2020:4035
---
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):
https://access.redhat.com/security/cve/c
Bugzilla
CVE-2020-8608 QEMU: Slirp: potential OOB access due to unsafe snprintf() usages
bugzilla·2020-02-05·CVSS 5.6
CVE-2020-8608 [MEDIUM] CVE-2020-8608 QEMU: Slirp: potential OOB access due to unsafe snprintf() usages
CVE-2020-8608 QEMU: Slirp: potential OOB access due to unsafe snprintf() usages
A out-of-bounds heap buffer access issue was found in the SLiRP networking implementation
of the QEMU emulator. It occurs in tcp_emu() routine while emulating IRC and
other protocols due to unsafe usage of snprintf(3) function.
A user/process could use this flaw to crash the Qemu process on the host
resulting in DoS or potentially execute arbitrary code with privileges of the
QEMU process on the host. Also with SELinux and sVirt access control in
place, malicious activity is restricted.
Upstream patch:
-> https://gitlab.freedesktop.org/slirp/libslirp/commit/68ccb8021a838066f0951d4b2817eb6b6f10a843
-> https://gitlab.freedesktop.org/slirp/libslirp/commit/30648c03b27fb8d9611b723184216cd3174b6775
Reference:
->
Bugzilla
CVE-2020-8608 qemu: Slirp: potential OOB access due to unsafe snprintf() usages [fedora-all]
bugzilla·2020-02-05·CVSS 5.6
CVE-2020-8608 [MEDIUM] CVE-2020-8608 qemu: Slirp: potential OOB access due to unsafe snprintf() usages [fedora-all]
CVE-2020-8608 qemu: Slirp: potential OOB access due to unsafe snprintf() usages [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple sup
Unit42
Rootless Containers: The Next Trend in Container Security
blogs_unit42·2020-05-26
Rootless Containers: The Next Trend in Container Security
Threat Research Center
Threat Research
Cloud Cybersecurity Research
## Rootless Containers: The Next Trend in Container Security
Aviv Sasson
Published: May 26, 2020
Cloud Cybersecurity Research
Threat Research
Podman LXC Container Security
Rootless Containers
Slirp
## Executive Summary
As cloud computing evolves, containers continue to become more and more popular. New solutions and ideas to the way we implement containers are being introduced. One of these new ideas is rootless containers.
Rootless containers is a new concept of containers that don’t require root privileges in order to formulate. Many solutions have been proposed to overcome the technological challenges of creating a container with an unprivileged user, some of them are still under development and some ar
Unit42
Rootless Containers: The Next Trend in Container Security
blogs_unit42·2020-05-26
Rootless Containers: The Next Trend in Container Security
## Executive Summary
As cloud computing evolves, containers continue to become more and more popular. New solutions and ideas to the way we implement containers are being introduced. One of these new ideas is rootless containers.
Rootless containers is a new concept of containers that don’t require root privileges in order to formulate. Many solutions have been proposed to overcome the technological challenges of creating a container with an unprivileged user, some of them are still under development and some are production-ready. While rootless containers present some advantages, mainly from a security perspective, they are still in their early stages.
In this post, Unit 42 researcher Aviv Sasson reviews the internals of rootless containers. Aviv also presents a vulnerability he found
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00007.htmlhttps://gitlab.freedesktop.org/slirp/libslirp/-/tags/v4.1.0https://gitlab.freedesktop.org/slirp/libslirp/commit/68ccb8021a838066f0951d4b2817eb6b6f10a843https://lists.debian.org/debian-lts-announce/2020/03/msg00015.htmlhttps://lists.debian.org/debian-lts-announce/2020/03/msg00017.htmlhttps://lists.debian.org/debian-lts-announce/2020/07/msg00020.htmlhttps://lists.debian.org/debian-lts-announce/2021/02/msg00012.htmlhttps://security.gentoo.org/glsa/202003-66https://security.netapp.com/advisory/ntap-20201001-0002/https://usn.ubuntu.com/4283-1/https://www.debian.org/security/2020/dsa-4733https://www.openwall.com/lists/oss-security/2020/02/06/2http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00007.htmlhttps://gitlab.freedesktop.org/slirp/libslirp/-/tags/v4.1.0https://gitlab.freedesktop.org/slirp/libslirp/commit/68ccb8021a838066f0951d4b2817eb6b6f10a843https://lists.debian.org/debian-lts-announce/2020/03/msg00015.htmlhttps://lists.debian.org/debian-lts-announce/2020/03/msg00017.htmlhttps://lists.debian.org/debian-lts-announce/2020/07/msg00020.htmlhttps://lists.debian.org/debian-lts-announce/2021/02/msg00012.htmlhttps://security.gentoo.org/glsa/202003-66https://security.netapp.com/advisory/ntap-20201001-0002/https://usn.ubuntu.com/4283-1/https://www.debian.org/security/2020/dsa-4733https://www.openwall.com/lists/oss-security/2020/02/06/2
2020-02-06
Published