ip_reass in ip_input.c in libslirp 4.0.0 has a heap-based buffer overflow via a large…
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.
No Libslirp Project vulnerabilities are listed in CISA KEV.
13 records in Libslirp · all components
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.
tftp.c in libslirp 4.1.0, as used in QEMU 4.2.0, does not prevent ..\ directory traversal on Windows.
libslirp 4.0.0, as used in QEMU 4.1.0, has a use-after-free in ip_reass in ip_input.c.
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.
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.
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 read vulnerability was found in the SLiRP networking implementation of the QEMU emulator.
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.
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.
An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU.
An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU.
An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU.
An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU.