Lucene search
+L

8 matches found

osv_jlsec
osv_jlsec
•added 2026/08/21 8:43 p.m.•37 views

JLSEC-2026-1348 Wasmtime doesn't fully sandbox all the Windows device filenames

Impact Wasmtime'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...

10CVSS5.9AI score0.00836EPSS
SaveExploits0References7
NVD
NVD
•added 2024/11/05 10:15 p.m.•47 views

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...

2.3CVSS0.00583EPSS
SaveExploits0References5
NVD
NVD
•added 2024/11/05 10:15 p.m.•28 views

CVE-2024-51745

Wasmtime is a fast and secure runtime for WebAssembly. Wasmtime'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,...

10CVSS0.00836EPSS
SaveExploits0References4
Vulnrichment
Vulnrichment
•added 2024/11/05 10:06 p.m.•22 views

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...

2.3CVSS5.9AI score0.00583EPSS
SaveExploits0References5
Mend
Mend
•added 2024/11/05 10:06 p.m.•16 views

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...

6.3CVSS5.9AI score0.00583EPSS
SaveExploits0References10
Cvelist
Cvelist
•added 2024/11/05 10:06 p.m.•40 views

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...

2.3CVSS0.00583EPSS
SaveExploits0References5
CVE
CVE
•added 2024/11/05 9:09 p.m.•325 views

CVE-2024-51745

Wasmtime on Windows had a sandbox bypass where filenames with superscript digits (e.g., COM¹, LPT⁰) were not blocked, allowing untrusted Wasm code with filesystem access to reach devices and peripherals via special device filenames. Affected software: Wasmtime’s Windows filesystem sandbox. Root c...

10CVSS5.9AI score0.00836EPSS
SaveExploits0References4Affected Software1
Vulnrichment
Vulnrichment
•added 2024/11/05 9:09 p.m.•14 views

CVE-2024-51745 Wasmtime doesn't fully sandbox all the Windows device filenames

Wasmtime is a fast and secure runtime for WebAssembly. Wasmtime'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,...

2.3CVSS5.9AI score0.00836EPSS
SaveExploits0References4
Rows per page
Query Builder