Directory Traversal Affecting wasmtime package, versions <26.0.1-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-WASMTIME-8352835
- published7 Nov 2024
- disclosed5 Nov 2024
Introduced: 5 Nov 2024
CVE-2024-51756 (opens in a new tab)How to fix?
Upgrade Chainguard wasmtime to version 26.0.1-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream wasmtime package and not the wasmtime package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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 it did not block access to the special device filenames which use superscript digits, such as "COM¹", "COM²", "LPT⁰", "LPT¹", and so on. Untrusted filesystem paths could bypass the sandbox and access devices through those special device filenames with superscript digits, and through them provide 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. The bug is fixed in #371, which is published in cap-primitives 3.4.1, cap-std 3.4.1, and cap-async-std 3.4.1. There are no known workarounds for this issue. Affected Windows users are recommended to upgrade.
References
- https://en.wikipedia.org/wiki/ISO/IEC_8859-1
- https://github.com/bytecodealliance/cap-std/commit/dcc3818039761331fbeacbb3a40c542b65b5ebf7
- https://github.com/bytecodealliance/cap-std/pull/371
- https://github.com/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw
- https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions