目标达成 感谢每一位支持者 — 我们达成了 100% 目标！

目标: 1000 元 · 已筹: 1336 元

100%
请我们喝杯咖啡

CVE-2022-39392— Wasmtime 缓冲区错误漏洞

一分钟漏洞结论

影响对象
bytecodealliance wasmtime
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。

Wasmtime是一个字节码联盟项目，它是一个独立的仅用于 WebAssembly 和 WASI 的 wasm 优化运行时。 Wasmtime 2.0.2之前的版本存在安全漏洞，该漏洞源于其零内存页配置的越界读写。

CVSS 5.9 · Medium EPSS 0.60% · P46

可能的 ATT&CK 技术 1 AI

T1406
获取后续新漏洞提醒 登录后订阅

一、 漏洞 CVE-2022-39392 基础信息

漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗

尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。

Vulnerability Title
Wasmtime vulnerable to out of bounds read/write with zero-memory-pages configuration
来源: CVE Program / CVE List V5
Vulnerability Description
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 Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
来源: CVE Program / CVE List V5
Vulnerability Type
内存缓冲区边界内操作的限制不恰当
来源: CVE Program / CVE List V5
Vulnerability Title
Wasmtime 缓冲区错误漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Wasmtime是一个字节码联盟项目，它是一个独立的仅用于 WebAssembly 和 WASI 的 wasm 优化运行时。 Wasmtime 2.0.2之前的版本存在安全漏洞，该漏洞源于其零内存页配置的越界读写。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD

受影响产品

厂商 产品 影响版本 CPE 订阅
bytecodealliance wasmtime < 2.0.2 -

二、漏洞 CVE-2022-39392 的公开POC

# POC 描述 源链接 神龙链接
AI 生成 POC 高级

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2022-39392 的情报信息

请登录查看更多情报信息。

CVE-2022-39392 补丁与修复 (1)

CVE-2022-39392 厂商安全公告 (1)

同批安全公告 · bytecodealliance · 2022-11-10 · 共 3 条

CVE-2022-39393 8.6 HIGH Wasmtime 安全漏洞
CVE-2022-39394 3.8 LOW Wasmtime 缓冲区错误漏洞

IV. Related Vulnerabilities

Same product: wasmtime
Same vendor: bytecodealliance
Same weakness: CWE-119

V. Comments for CVE-2022-39392

暂无评论

发表评论