Vulnerability RUSTSEC-2024-0438
Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
1 year ago
November 02, 2024 at 12:00 PM UTC
Wasmtime doesn't fully sandbox all the Windows device filenames
0.0.0 - 24.0.1
0.0.0 - 24.0.1
Summary
Wasmtime doesn't fully sandbox all the Windows device filenames
Details
This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-c2f5-jxjv-2hh8. For more information see the GitHub-hosted security advisory.
Related Vulnerabilities
Other vulnerabilities affecting the same packages
Low Risk
9 days ago
Wasmtime: Preemption and traps during bulk operations enable breaking internal VM state
46.0.0 - 46.0.1 and 47.0.0 - 47.0.2 GHSA-2hw9-mc66-jc2q
46.0.0 - 46.0.1 and 47.0.0 - 47.0.2 GHSA-2hw9-mc66-jc2q
Unknown
10 days ago
Mis-typed WebAssembly tag imports can lead to GC heap corruption
47.0.0 - 48.0.3 RUSTSEC-2026-0325
47.0.0 - 48.0.3 RUSTSEC-2026-0325
Medium Risk
10 days ago
Rooting for GC values live across `try_call` may be missing, causing GC heap corruption
47.0.0 - 48.0.3 RUSTSEC-2026-0326
47.0.0 - 48.0.3 RUSTSEC-2026-0326
Unknown
10 days ago
Wasmtime component async-lifted callback result count is unvalidated, causing a native stack buffer overflow
39.0.0 - 48.0.3 RUSTSEC-2026-0327
39.0.0 - 48.0.3 RUSTSEC-2026-0327
Medium Risk
18 days ago
`call_ref` and exception `catch` can drop some fuel accounting, leading to exponential fuel amplification
47.0.0 - 48.0.2 RUSTSEC-2026-0315
47.0.0 - 48.0.2 RUSTSEC-2026-0315
Impacted packages
Timeline
Published
1 year ago
November 02, 2024 at 12:00 PM UTC
Fixed (24.0.2)
1 year ago
November 05, 2024 at 07:21 PM UTC
Fixed (26.0.1)
1 year ago
November 05, 2024 at 07:25 PM UTC
Fixed (25.0.3)
1 year ago
November 05, 2024 at 07:25 PM UTC
Last Modified
1 hour ago
October 12, 2026 at 06:00 PM UTC