Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2024-51756— cap-std doesn't fully sandbox all the Windows device filenames

Quick assessment

Affected
bytecodealliance cap-std
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

cap-std是Bytecode Alliance开源的一个基于功能的 Rust 标准库版本。 cap-std 3.4.1之前版本存在路径遍历漏洞，该漏洞源于在Windows上的文件系统沙箱实现未能阻止对使用上标数字的特殊设备文件名的访问。

AI Predicted 8.1 Difficulty: Easy EPSS 0.58% · P46

Possible ATT&CK Techniques 1 AI

T1564.004 · NTFS File Attributes
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-51756

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
cap-std doesn't fully sandbox all the Windows device filenames
Source: CVE Program / CVE List V5
Vulnerability Description
The cap-std project is organized around the eponymous `cap-std` crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however it did not block access to the special device filenames which use superscript digits, such as "COM¹", "COM²", "LPT⁰", "LPT¹", and so on. Untrusted filesystem paths could bypass the sandbox and access devices through those special device filenames with superscript digits, and through them provide access peripheral devices connected to the computer, or network resources mapped to those devices. This can include modems, printers, network printers, and any other device connected to a serial or parallel port, including emulated USB serial ports. The bug is fixed in #371, which is published in cap-primitives 3.4.1, cap-std 3.4.1, and cap-async-std 3.4.1. There are no known workarounds for this issue. Affected Windows users are recommended to upgrade.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
对路径名的限制不恰当(路径遍历)
Source: CVE Program / CVE List V5
Vulnerability Title
cap-std 路径遍历漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
cap-std是Bytecode Alliance开源的一个基于功能的 Rust 标准库版本。 cap-std 3.4.1之前版本存在路径遍历漏洞，该漏洞源于在Windows上的文件系统沙箱实现未能阻止对使用上标数字的特殊设备文件名的访问。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
bytecodealliance cap-std < 3.4.1 -

II. Public POCs for CVE-2024-51756

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-51756

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

Vendor Advisories for CVE-2024-51756 (2)

Other References for CVE-2024-51756 (1)

IV. Related Vulnerabilities

Same vendor: bytecodealliance
Same weakness: CWE-22

V. Comments for CVE-2024-51756

No comments yet

Leave a comment