CVE-2024-51745: Wasmtime doesn't fully sandbox all the Windows device filenames
(updated )
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 on. Untrusted Wasm programs that are given access to any filesystem directory could bypass the sandbox and access devices through those special device filenames with superscript digits, and through them gain access peripheral devices connected to the computer, or network resources mapped to those devices. This can include modems, printers, network printers, and any other device connected to a serial or parallel port, including emulated USB serial ports.
References
- en.wikipedia.org/wiki/ISO/IEC_8859-1
- github.com/advisories/GHSA-c2f5-jxjv-2hh8
- github.com/bytecodealliance/cap-std/pull/371
- github.com/bytecodealliance/wasmtime
- github.com/bytecodealliance/wasmtime/security/advisories/GHSA-c2f5-jxjv-2hh8
- learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file
- nvd.nist.gov/vuln/detail/CVE-2024-51745
Detect and mitigate CVE-2024-51745 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →