Libslirp Libslirpproject Libslirp

Do you want an email whenever new security vulnerabilities are reported in Libslirpproject Libslirp?

By the Year

In 2022 there have been 0 vulnerabilities in Libslirpproject Libslirp . Last year Libslirp had 4 security vulnerabilities published. Right now, Libslirp is on track to have less security vulnerabilities in 2022 than it did last year.

Year Vulnerabilities Average Score
2022 0 0.00
2021 4 3.80
2020 6 5.47
2019 2 8.15
2018 0 0.00

It may take a day or so for new Libslirp vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Libslirpproject Libslirp Security Vulnerabilities

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU

CVE-2021-3595 3.8 - Low - June 15, 2021

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the tftp_input() function and could occur while processing a udp packet that is smaller than the size of the 'tftp_t' structure. This issue may lead to out-of-bounds read access or indirect host memory disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw affects libslirp versions prior to 4.6.0.

Access of Uninitialized Pointer

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU

CVE-2021-3594 3.8 - Low - June 15, 2021

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the udp_input() function and could occur while processing a udp packet that is smaller than the size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or indirect host memory disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw affects libslirp versions prior to 4.6.0.

Access of Uninitialized Pointer

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU

CVE-2021-3593 3.8 - Low - June 15, 2021

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the udp6_input() function and could occur while processing a udp packet that is smaller than the size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or indirect host memory disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw affects libslirp versions prior to 4.6.0.

Access of Uninitialized Pointer

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU

CVE-2021-3592 3.8 - Low - June 15, 2021

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the bootp_input() function and could occur while processing a udp packet that is smaller than the size of the 'bootp_t' structure. A malicious guest could use this flaw to leak 10 bytes of uninitialized heap memory from the host. The highest threat from this vulnerability is to data confidentiality. This flaw affects libslirp versions prior to 4.6.0.

Access of Uninitialized Pointer

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

CVE-2020-29129 4.3 - Medium - November 26, 2020

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 exceeds the total packet length.

Out-of-bounds Read

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

CVE-2020-29130 4.3 - Medium - November 26, 2020

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 exceeds the total packet length.

Out-of-bounds Read

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

CVE-2020-10756 6.5 - Medium - July 09, 2020

An out-of-bounds read vulnerability was found in the SLiRP networking implementation of the QEMU emulator. This flaw occurs in the icmp6_send_echoreply() routine while replying to an ICMP echo request, also known as ping. This flaw allows a malicious guest to leak the contents of the host memory, resulting in possible information disclosure. This flaw affects versions of libslirp before 4.3.1.

Out-of-bounds Read

A use after free vulnerability in ip_reass() in ip_input.c of libslirp 4.2.0 and prior releases

CVE-2020-1983 6.5 - Medium - April 22, 2020

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 denial of service.

Dangling pointer

In libslirp 4.1.0

CVE-2020-8608 5.6 - Medium - February 06, 2020

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.

Classic Buffer Overflow

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

CVE-2020-7039 5.6 - Medium - January 16, 2020

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. This can cause a heap-based buffer overflow or other out-of-bounds access which can lead to a DoS or potential execute arbitrary code.

Memory Corruption

libslirp 4.0.0

CVE-2019-15890 7.5 - High - September 06, 2019

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

Dangling pointer

ip_reass in ip_input.c in libslirp 4.0.0 has a heap-based buffer overflow via a large packet

CVE-2019-14378 8.8 - High - July 29, 2019

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 involving the first fragment.

Memory Corruption

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Libslirpproject Libslirp or by Libslirpproject? Click the Watch button to subscribe.

subscribe