CVSS: 5.3EPSS: 0%CPEs: 3EXPL: 0CVE-2023-5871 – Libnbd: malicious nbd server may crash libnbd
https://notcve.org/view.php?id=CVE-2023-5871
A flaw was found in libnbd, due to a malicious Network Block Device (NBD), a protocol for accessing Block Devices such as hard disks over a Network. This issue may allow a malicious NBD server to cause a Denial of Service. Se encontró una falla en libnbd debido a un Network Block Device (NBD) malicioso, un protocolo para acceder a dispositivos de bloque, como discos duros, a través de una red. Este problema puede permitir que un servidor NBD malintencionado provoque una Denegación de Servicio. • https://access.redhat.com/errata/RHSA-2024:2204 https://access.redhat.com/security/cve/CVE-2023-5871 https://bugzilla.redhat.com/show_bug.cgi?id=2247308 https://lists.libguestfs.org/archives/list/guestfs@lists.libguestfs.org/thread/PFVUCMPFQUDC23JXSCUUPXIGDZ7XCFMD • CWE-617: Reachable Assertion •
CVSS: 6.5EPSS: 0%CPEs: 3EXPL: 1CVE-2023-5215 – Libnbd: crash or misbehaviour when nbd server returns an unexpected block size
https://notcve.org/view.php?id=CVE-2023-5215
A flaw was found in libnbd. A server can reply with a block size larger than 2^63 (the NBD spec states the size is a 64-bit unsigned value). This issue could lead to an application crash or other unintended behavior for NBD clients that doesn't treat the return value of the nbd_get_size() function correctly. Se encontró una falla en libnbd. Un servidor puede responder con un tamaño de bloque mayor que 2^63 (la especificación NBD establece que el tamaño es un valor sin signo de 64 bits). • https://access.redhat.com/errata/RHSA-2024:2204 https://access.redhat.com/security/cve/CVE-2023-5215 https://bugzilla.redhat.com/show_bug.cgi?id=2241041 https://listman.redhat.com/archives/libguestfs/2023-September/032635.html • CWE-241: Improper Handling of Unexpected Data Type CWE-252: Unchecked Return Value •
CVSS: 4.8EPSS: 0%CPEs: 2EXPL: 1CVE-2022-0485 – libnbd: nbdcopy: missing error handling may create corrupted destination image
https://notcve.org/view.php?id=CVE-2022-0485
A flaw was found in the copying tool `nbdcopy` of libnbd. When performing multi-threaded copies using asynchronous nbd calls, nbdcopy was blindly treating the completion of an asynchronous command as successful, rather than checking the *error parameter. This could result in the silent creation of a corrupted destination image. Se ha encontrado un fallo en la herramienta de copia "nbdcopy" de libnbd. Cuando eran llevado a cabo copias multihilo usando llamadas asíncronas a nbd, nbdcopy trataba ciegamente la finalización de un comando asíncrono como exitosa, en lugar de comprobar el parámetro *error. • https://access.redhat.com/security/cve/CVE-2022-0485 https://bugzilla.redhat.com/show_bug.cgi?id=2046194 https://bugzilla.redhat.com/show_bug.cgi?id=2050324 https://gitlab.com/nbdkit/libnbd/-/commit/8d444b41d09a700c7ee6f9182a649f3f2d325abb https://listman.redhat.com/archives/libguestfs/2022-February/msg00104.html • CWE-252: Unchecked Return Value •
CVSS: 4.0EPSS: 0%CPEs: 2EXPL: 0CVE-2021-20286
https://notcve.org/view.php?id=CVE-2021-20286
A flaw was found in libnbd 1.7.3. An assertion failure in nbd_unlocked_opt_go in ilb/opt.c may lead to denial of service. Se encontró un fallo en libnbd versión 1.7.3. Un error de aserción en la función nbd_unlocked_opt_go en la biblioteca ilb/opt.c puede causar una denegación de servicio • https://bugzilla.redhat.com/show_bug.cgi?id=1934727 https://gitlab.com/nbdkit/libnbd/-/commit/fb4440de9cc76e9c14bd3ddf3333e78621f40ad0 • CWE-617: Reachable Assertion •
CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0CVE-2019-14842
https://notcve.org/view.php?id=CVE-2019-14842
Structured reply is a feature of the newstyle NBD protocol allowing the server to send a reply in chunks. A bounds check which was supposed to test for chunk offsets smaller than the beginning of the request did not work because of signed/unsigned confusion. If one of these chunks contains a negative offset then data under control of the server is written to memory before the read buffer supplied by the client. If the read buffer is located on the stack then this allows the stack return address from nbd_pread() to be trivially modified, allowing arbitrary code execution under the control of the server. If the buffer is located on the heap then other memory objects before the buffer can be overwritten, which again would usually lead to arbitrary code execution. • https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14842 https://www.redhat.com/archives/libguestfs/2019-October/msg00060.html • CWE-681: Incorrect Conversion between Numeric Types •