RUSTSEC-2026-0486: xattr functions mark unwritten bytes as initialized when given a zero-length buffer
還沒有人認領這個 Issue。
評估
研究方向
Start in Cargo.toml and Cargo.lock, where the rustix dependency is pinned at 1.1.4. Search the source for calls to getxattr, lgetxattr, fgetxattr, listxattr, llistxattr or flistxattr to see whether this crate uses them at all. Done means rustix is raised to 1.1.6 or later, any call sites are adjusted to the new empty-result behavior, and cargo build and cargo test pass.
由索引模型根據 Issue 內容生成。
描述
xattr functions mark unwritten bytes as initialized when given a zero-length buffer
| Details | |
|---|---|
| Status | unsound |
| Package | rustix |
| Version | 1.1.4 |
| URL | https://github.com/bytecodealliance/rustix/commit/8e6aaa6713d2bb64b1fdd8c472e3a32a10a76d70 |
| Date | 2026-10-27 |
The extended-attribute functions in rustix::fs (getxattr, lgetxattr, fgetxattr, listxattr, llistxattr and flistxattr) write into a Buffer and then mark as many bytes initialized as the system call reported. When the buffer has zero length, the operating system treats the call as a size query: it writes nothing and returns the size of the attribute value or of the name list. rustix still marked that many bytes as initialized.
Passing a Vec whose length equals its capacity through spare_capacity gives such a zero-length buffer, and rustix then set the vector's length past its capacity over memory that was never written. This is undefined behavior reachable from safe code. With an empty &mut [MaybeUninit<u8>] the call panics instead.
From 1.1.6 these functions return an empty result for a zero-length buffer, and new getxattr_query, lgetxattr_query, fgetxattr_query, listxattr_query, llistxattr_query and flistxattr_query functions return the size. The 0.38 series did not have the Buffer API and is not affected.
See advisory page for additional details.
- 主要語言
- Rust
- 星號
- 0
- 分支
- 1
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 82/100
storytold/photocraft#14822 ·
維護者通常 1 天內回覆
-
bug css
難度 2/5 1-3 小時 新手友好度 66/100
dginev/latexml-oxide#853 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
維護者通常 2 天內回覆
-
[Bug] export_build_environment admits its output directory only after the export ran in the build computer可能已有人在做 @viniciusdsandrade 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 62/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆