Vulnerabilities
Last updated 57 minutes ago
| Package | Summary | Severity | Published | Modified |
|---|---|---|---|---|
wasmtime-wasi
|
WASI hard links and renames bypass wasmtime-wasi's FilePerms for destination | Medium Risk 6.5 | 3 months ago | 2 hours ago |
wasmtime-wasi
|
WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction | High Risk 7.5 | 4 months ago | 2 hours ago |
wasmtime-wasi
|
Leak in WASIp1 `fd_renumber` implementation | Unknown | 3 months ago | 2 hours ago |
wasmtime-wasi-http
|
Wasmtime wasi:http implementation panics with a zero timeout supplied | Unknown | 10 days ago | 9 days ago |
wasmtime-wasi
|
WASI preview 0 implementation of `poll_oneoff` circumvents fuel consumption | Medium Risk 4.0 | 10 days ago | 9 days ago |
wasmtime-wasi
|
Excessive allocated memory on the host when guests don't have stdio | Unknown | 10 days ago | 9 days ago |
wasmtime-wasi
|
fd_readdir copies uninitialized struct padding into guest memory | Unknown | 10 days ago | 9 days ago |
wasmtime-wasi
|
Guest can panic host through filesystem timestamp before the epoch on wasip3 | Medium Risk 6.2 | 10 days ago | 9 days ago |
wasmtime-wasi-http
|
Outgoing HTTP body write allows guest-driven host memory exhaustion | Medium Risk 6.2 | 18 days ago | 13 days ago |
wasmtime-wasi
|
Guest can panic host through filesystem datetime overflow | Medium Risk 6.2 | 18 days ago | 13 days ago |
wasmtime-wasi
|
wasmtime-wasi: WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction | High Risk 7.5 | 4 months ago | 1 month ago |
wasmtime-wasi
|
Wasmtime CLI is vulnerable to host panic through its fd_renumber function | Low Risk 3.5 | 1 year ago | 1 month ago |
wasmtime-wasi
|
Wasmtime has a leak in WASIp1 `fd_renumber` implementation | Medium Risk 5.0 | 1 month ago | 1 month ago |
Page 1