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

目标: 1000 元 · 已筹: 1359 元

100%
请我们喝杯咖啡

CVE-2021-39219— Wasmtime 代码问题漏洞

一分钟漏洞结论

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

Wasmtime是一个字节码联盟项目，它是一个独立的仅用于 WebAssembly 和 WASI 的 wasm 优化运行时。 Wasmtime 存在代码问题漏洞，该漏洞源于 0.30.0 版本之前的 Wasmtime 受类型混淆漏洞影响。

CVSS 6.3 · Medium EPSS 0.36% · P28
获取后续新漏洞提醒 登录后订阅

一、 漏洞 CVE-2021-39219 基础信息

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

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

Vulnerability Title
Wrong type for `Linker`-define functions when used across two `Engine`s
来源: CVE Program / CVE List V5
Vulnerability Description
Wasmtime is an open source runtime for WebAssembly & WASI. Wasmtime before version 0.30.0 is affected by a type confusion vulnerability. As a Rust library the `wasmtime` crate clearly marks which functions are safe and which are `unsafe`, guaranteeing that if consumers never use `unsafe` then it should not be possible to have memory unsafety issues in their embeddings of Wasmtime. An issue was discovered in the safe API of `Linker::func_*` APIs. These APIs were previously not sound when one `Engine` was used to create the `Linker` and then a different `Engine` was used to create a `Store` and then the `Linker` was used to instantiate a module into that `Store`. Cross-`Engine` usage of functions is not supported in Wasmtime and this can result in type confusion of function pointers, resulting in being able to safely call a function with the wrong type. Triggering this bug requires using at least two `Engine` values in an embedding and then additionally using two different values with a `Linker` (one at the creation time of the `Linker` and another when instantiating a module with the `Linker`). It's expected that usage of more-than-one `Engine` in an embedding is relatively rare since an `Engine` is intended to be a globally shared resource, so the expectation is that the impact of this issue is relatively small. The fix implemented is to change this behavior to `panic!()` in Rust instead of silently allowing it. Using different `Engine` instances with a `Linker` is a programmer bug that `wasmtime` catches at runtime. This bug has been patched and users should upgrade to Wasmtime version 0.30.0. If you cannot upgrade Wasmtime and are using more than one `Engine` in your embedding it's recommended to instead use only one `Engine` for the entire program if possible. An `Engine` is designed to be a globally shared resource that is suitable to have only one for the lifetime of an entire process. If using multiple `Engine`s is required then code should be audited to ensure that `Linker` is only used with one `Engine`.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
使用不兼容类型访问资源(类型混淆)
来源: CVE Program / CVE List V5
Vulnerability Title
Wasmtime 代码问题漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Wasmtime是一个字节码联盟项目，它是一个独立的仅用于 WebAssembly 和 WASI 的 wasm 优化运行时。 Wasmtime 存在代码问题漏洞，该漏洞源于 0.30.0 版本之前的 Wasmtime 受类型混淆漏洞影响。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD

受影响产品

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

二、漏洞 CVE-2021-39219 的公开POC

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

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2021-39219 的情报信息

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

CVE-2021-39219 补丁与修复 (1)

CVE-2021-39219 厂商安全公告 (1)

CVE-2021-39219 邮件列表归档 (2)

CVE-2021-39219 其他参考 (1)

同批安全公告 · bytecodealliance · 2021-09-17 · 共 3 条

CVE-2021-39216 6.3 MEDIUM Wasmtime 资源管理错误漏洞
CVE-2021-39218 6.3 MEDIUM Wasmtime 缓冲区错误漏洞

IV. Related Vulnerabilities

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

V. Comments for CVE-2021-39219

暂无评论

发表评论