Wasmtime: WASI hard links bypass wasmtime-wasi's FilePerms for destination
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 24.0.11, 36.0.12, 45.0.3, 46.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Wasmtime is a runtime for WebAssembly. Prior to 24.0.11, 36.0.12, 45.0.3, and 46.0.1, wasmtime-wasi hard-link creation and renaming check directory permissions but not matching FilePerms on source and destination preopens, allowing a WASI guest with a read-only source file capability to overwrite host files exposed as FilePerms::READ through wasip1, wasip2, or wasip3 filesystem interfaces. This issue is fixed in versions 24.0.11, 36.0.12, 45.0.3, and 46.0.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- bytecodealliance wasmtime
fixed in 24.0.11; From 25.0.0 · fixed in 36.0.12; From 37.0.0 · fixed in 45.0.3; From 46.0.0 · fixed in 46.0.1
- wasmtime-wasicrates.io
fixed in 24.0.11
- wasmtime-wasicrates.io
From 25.0.0 · fixed in 36.0.12
- wasmtime-wasicrates.io
From 37.0.0 · fixed in 45.0.3
- wasmtime-wasicrates.io
From 46.0.0 · fixed in 46.0.1
- wasmtime-wasicrates.io
From 0.0.0-0 · fixed in 24.0.11; From 25.0.0 · fixed in 36.0.12; From 37.0.0 · fixed in 45.0.3; From 46.0.0 · fixed in 46.0.1