CVE-2021-3595

< 4.6.0

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the tftp_inpu

3.8LOW

CVE-2021-3594

< 4.6.0

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the udp_input

3.8LOW

CVE-2021-3593

< 4.6.0

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the udp6_inpu

3.8LOW

CVE-2021-3592

< 4.6.0

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the bootp_inp

3.8LOW

CVE-2020-29130

<= 4.3.1

slirp.c in libslirp through 4.3.1 has a buffer over-read because it tries to read a certain amount of header data even if that exc

4.3MEDIUM

CVE-2020-29129

<= 4.3.1

ncsi.c in libslirp through 4.3.1 has a buffer over-read because it tries to read a certain amount of header data even if that exce

4.3MEDIUM

CVE-2020-10756

< 4.3.1

An out-of-bounds read vulnerability was found in the SLiRP networking implementation of the QEMU emulator. This flaw occurs in the

6.5MEDIUM

CVE-2020-1983

<= 4.2.0

A use after free vulnerability in ip_reass() in ip_input.c of libslirp 4.2.0 and prior releases allows crafted packets to cause a

7.5HIGH

CVE-2020-8608

all versions

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.

5.6MEDIUM

CVE-2020-7211

all versions

tftp.c in libslirp 4.1.0, as used in QEMU 4.2.0, does not prevent ..\ directory traversal on Windows.

7.5HIGH

CVE-2020-7039

all versions

tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC DCC commands in EMU_IRC.

5.6MEDIUM

CVE-2019-15890

all versions

libslirp 4.0.0, as used in QEMU 4.1.0, has a use-after-free in ip_reass in ip_input.c.

7.5HIGH

CVE-2019-14378

all versions

ip_reass in ip_input.c in libslirp 4.0.0 has a heap-based buffer overflow via a large packet because it mishandles a case involvin

8.8HIGH