CVE-2024-47603

GStreamer is a library for constructing graphs of media-handling components. A null pointer dereference vulnerability has been discovered in the gstmatroskademuxupdatetracks function within matroska-demux.c. The vulnerability occurs when the gstcapsisequal function is called with invalid caps...

GHSA-PQHP-25J4-6HQ9 smol-toml has a Denial of Service via malicious TOML document using deeply nested inline tables

Summary An attacker can send a maliciously crafted TOML to cause the parser to crash because of a stack overflow caused by a deeply nested inline structure. A similar problem occurs when attempting to stringify deeply nested objects. The library does not limit the maximum exploration depth while...

CVE-2024-50289: Undefined Security Weakness

In the Linux kernel, the following vulnerability has been resolved: media: av7110: fix a spectre vulnerability As warned by smatch: drivers/staging/media/av7110/av7110ca.c:270 dvbcaioctl warn: potential spectre issue 'av7110-cislot' w local cap There is a spectre-related vulnerability at the code...

kernel: virtio-blk: fix implicit overflow on virtio_max_dma_size

In the Linux kernel, the following vulnerability has been resolved: virtio-blk: fix implicit overflow on virtiomaxdmasize The following codes have an implicit conversion from sizet to u32: u32maxsize = sizetvirtiomaxdmasizevdev; This may lead overflow, Ex sizet4G - u320. Once virtiomaxdmasize has...

gpiocdev (>=0.4.3, <=0.7.0), gpiocdev-embedded-hal (0.1.0) +1 more potentially affected by CVE-2024-51756 via cap-primitives (3.0.0)

cap-primitives CARGO version 3.0.0 is affected by a known vulnerability. The following packages have a transitive dependency on cap-primitives and may be impacted: - gpiocdev =0.4.3, =0.16.0, =0.16.3 Source cves: CVE-2024-51756 Source advisory: OSV:GHSA-HXF5-99XG-86HW...

GHSA-HXF5-99XG-86HW cap-std doesn't fully sandbox all the Windows device filenames

Impact cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however it did not block access to the special device filenames which use superscript digits, such as "COM¹", "COM²", "LPT⁰", "LPT¹", and so o...

gpiocdev (>=0.4.3, <=0.7.0), gpiocdev-embedded-hal (0.1.0) +1 more potentially affected by CVE-2024-51756 via cap-std (3.0.0)

cap-std CARGO version 3.0.0 is affected by a known vulnerability. The following packages have a transitive dependency on cap-std and may be impacted: - gpiocdev =0.4.3, =0.16.0, =0.16.3 Source cves: CVE-2024-51756 Source advisory: OSV:GHSA-HXF5-99XG-86HW...

cap-std doesn't fully sandbox all the Windows device filenames

Impact cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however it did not block access to the special device filenames which use superscript digits, such as "COM¹", "COM²", "LPT⁰", "LPT¹", and so o...

CVE-2024-51756

The cap-std project is organized around the eponymous cap-std crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however i...

CVE-2024-51756

The cap-std project is organized around the eponymous "cap-std" crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however...

CVE-2024-51756 cap-std doesn't fully sandbox all the Windows device filenames

The cap-std project is organized around the eponymous cap-std crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however i...

CVE-2024-51756 cap-std doesn't fully sandbox all the Windows device filenames

The cap-std project is organized around the eponymous cap-std crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however i...

CVE-2024-51756

The CVE affects cap-std’s Windows filesystem sandbox, where access to special device filenames with superscript digits (e.g., COM¹, LPT⁰) was not blocked, allowing untrusted paths to bypass the sandbox and reach peripheral devices or network-shared resources mapped to those devices. Root cause: t...

CVE-2024-51756 cap-std doesn't fully sandbox all the Windows device filenames

The cap-std project is organized around the eponymous cap-std crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however i...

CVE-2024-51756

The cap-std project is organized around the eponymous cap-std crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however i...

gpiocdev (>=0.4.3, <=0.7.0), gpiocdev-embedded-hal (0.1.0) +1 more potentially affected by CVE-2024-51756 via cap-primitives (3.0.0)

cap-primitives CARGO version 3.0.0 is affected by a known vulnerability. The following packages have a transitive dependency on cap-primitives and may be impacted: - gpiocdev =0.4.3, =0.16.0, =0.16.3 Source cves: CVE-2024-51756 Source advisory: OSV:RUSTSEC-2024-0445...

cap-primitives doesn't fully sandbox all the Windows device filenames

Impact cap-primitives's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however it did not block access to the special device filenames which use superscript digits, such as "COM¹", "COM²", "LPT⁰", "LPT¹", a...

RUSTSEC-2024-0445 cap-primitives doesn't fully sandbox all the Windows device filenames

Impact cap-primitives's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however it did not block access to the special device filenames which use superscript digits, such as "COM¹", "COM²", "LPT⁰", "LPT¹", a...

CVE-2024-51756: Improper Limitation of a Pathname to a Restricted Directory

The cap-std project is organized around the eponymous cap-std crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however i...

PT-2024-34887 · Cap-Std +1 · Cap-Std +2

Name of the Vulnerable Software and Affected Versions: cap-std versions prior to 3.4.1 cap-primitives versions prior to 3.4.1 cap-async-std versions prior to 3.4.1 Description: The cap-std project's filesystem sandbox implementation on Windows has a flaw that allows untrusted filesystem paths to...