Red Hat libnbd 0.1.3

CPE Details

Red Hat libnbd 0.1.3
0.1.3
2020-10-07
17h38 +00:00
2020-10-07
17h38 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:redhat:libnbd:0.1.3:*:*:*:*:*:*:*

Informations

Vendor

redhat

Product

libnbd

Version

0.1.3

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2023-5215 2023-09-28 13h55 +00:00 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.
6.5
Medium
CVE-2022-0485 2022-08-29 12h03 +00:00 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.
4.8
Medium
CVE-2021-20286 2021-03-15 16h38 +00:00 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.
2.7
Low
CVE-2019-14842 2019-11-26 14h01 +00:00 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.
9.8
Critical