GHSA-44mr-8vmm-wjhg · 深刻度： medium · エコシステム： rust — Wasmtime out of bounds read/write with zero-memory-pages configuration
Wasmtime is a standalone runtime for WebAssembly. Prior to version 2.0.2, there is a bug in Wasmtime's implementation of its pooling instance allocator when the allocator is configured to give WebAssembly instances a maximum of zero pages of memory. In this configuration, the virtual memory mapping for WebAssembly memories did not meet the compiler-required configuration requirements for safely executing WebAssembly modules. Wasmtime's default settings require virtual memory page faults to indicate that wasm reads/writes are out-of-bounds, but the pooling allocator's configuration would not create an appropriate virtual memory mapping for this meaning out of bounds reads/writes can successfully read/write memory unrelated to the wasm sandbox within range of the base address of the memory mapping created by the pooling allocator. This bug is not applicable with the default settings of the `wasmtime` crate. This bug can only be triggered by setting `InstanceLimits::memory_pages` to zero. This is expected to be a very rare configuration since this means that wasm modules cannot allocate any pages of linear memory. All wasm modules produced by all current toolchains are highly likely to use linear memory, so it's expected to be unlikely that this configuration is set to zero by any production embedding of Wasmtime. This bug has been patched and users should upgrade to Wasmtime 2.0.2. This bug can be worked around by increasing the `memory_pages` allotment when configuring the pooling allocator to a value greater than zero. If an embedding wishes to still prevent memory from actually being used then the `Store::limiter` method can be used to dynamically disallow growth of memory beyond 0 bytes large. Note that the default `memory_pages` value is greater than zero.
総合評価: CVE-2022-39392 は低リスク（38.8/100）。CVSS 深刻度は中。悪用される可能性が高い（EPSS 0.58%、43 パーセンタイル） 推奨対応: 悪用情報と EPSS の推移を監視し、必要に応じて優先度を見直してください。
リスクは変動します。再評価に基づき、本ページの表示内容を更新しています。
EPSS は日次で悪用されやすさの相対度合いを推定します。パーセンタイルは採点済み CVE の中での相対位置（高いほど相対的に深刻）を示します。
| # | 日付 | 旧 EPSS スコア | 新 EPSS スコア | Δ（新 − 旧） |
|---|---|---|---|---|
| 1 | 2026-06-15 | 0.41% | 0.58% | +0.17% |
| 2 | 2026-06-10 | 0.24% | 0.41% | +0.17% |
| 3 | 2025-12-31 | — | 0.24% | — |
EPSS の全履歴 （全 10 件）
この CVE の CVSS 指標。
| ベーススコア | バージョン | 深刻度 | ベクトル | 悪用しやすさ | 影響 | スコアの出典 |
|---|---|---|---|---|---|---|
| 5.9 | 3.1 | MEDIUM |
|
0.7 | 5.2 | [email protected] |
| 7.4 | 3.1 | HIGH |
|
2.2 | 5.2 | [email protected] |
GHSA-44mr-8vmm-wjhg · 深刻度： medium · エコシステム： rust — Wasmtime out of bounds read/write with zero-memory-pages configuration
| vendor | priority | summary | link |
|---|---|---|---|
debian
|
unimportant | CVE-2022-39392 unimportant priority: Debian including 1 source packages (rust-wasmtime), 3 status rows across 3 suites (forky, sid, trixie): resolved 3. | https://security-tracker.debian.org/tracker/CVE-2022-39392 |
ubuntu
|
medium | CVE-2022-39392 medium priority: Ubuntu including 7 source packages (firefox, mozjs38, …), 58 status rows across 10 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, trusty, upstream, xenial): DNE 27, ignored 24, not-affected 5, needs-triage 2. | https://ubuntu.com/security/CVE-2022-39392 |
| ベンダー | 製品 | バージョン | 生の CPE |
|---|---|---|---|
| bytecodealliance | wasmtime | < 1.0.2 | cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:rust:*:* |
| bytecodealliance | wasmtime | >= 2.0.0, < 2.0.2 | cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:rust:*:* |
| URL | タグ |
|---|---|
| https://github.com/bytecodealliance/wasmtime/commit/e60c3742904ccbb3e26da201c9221c38a4981d72 | Patch Third Party Advisory |
| https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-44mr-8vmm-wjhg | Third Party Advisory |