A flaw was found in libnbd. A malicious actor could exploit this by convincing libnbd to open a specially crafted Uniform Resource Identifier (URI). This vulnerability arises because non-standard hostnames starting with '-o' are incorrectly interpreted as arguments to the Secure...
Product
redhat libnbd vulnerabilities
6 published CVES affecting redhat libnbd, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 1
- High
- 0
- Medium
- 4
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Latest redhat libnbd CVEs
Newest publication first
-
MediumCVSS 4.8 EPSS 0.14%
-
MediumCVSS 5.3 EPSS 1.1%
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.
-
CVE-2023-5215 Libnbd: crash or misbehaviour when nbd server returns an unexpected block size
PublishedMediumCVSS 6.5 EPSS 0.81%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_g...
-
MediumCVSS 4.8 EPSS 1.1%
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 si...
-
LowCVSS 2.7 EPSS 1.1%
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.
-
CriticalCVSS 9.8 EPSS 1.8%
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 chunk...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.