【高危】uu_mkfifo 安全更新（GHSA-pmf6-rcx4-v53v）

安全情报快照 · 风险级别：高危 · CVSS：7.1 · CVE-2026-35341 · GHSA-pmf6-rcx4-v53v

先看结论

uu_mkfifo存在安全风险，< 0.6.0 受影响，建议升级至 0.6.0。

影响范围

生态	组件	受影响版本	首个修复版本
rust	`uu_mkfifo`	< 0.6.0	0.6.0

处置建议

优先将 uu_mkfifo 升级至 0.6.0 或更高版本；升级前请结合业务依赖完成兼容性验证。

上游技术详情（原文）

When mkfifo() fails (e.g. target already exists), the code shows an error but is missing a continue;, so it falls through to fs::set_permissions and changes the permissions of the pre-existing file to the default FIFO mode (0o666 & umask -> 0644).

$ touch secret; chmod 000 secret
$ coreutils mkfifo secret fifo3 fifo4
mkfifo: cannot create fifo 'secret': File exists
$ ll secret      # uutils:
prw-r--r-- secret   # changed to 644 (GNU leaves it 000)

Impact: an attacker (or user error) can relax permissions on sensitive owner-only files such as SSH private keys, exposing them to other users. Recommendation: add continue; after the error.

Remediation: Acknowledged by Canonical; fixed in PR #10376.

Reported by Zellic in the uutils coreutils Program Security Assessment (prepared for Canonical, Jan 20 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242. Finding 3.8. Credit: Zellic.

Upstream tracking issue: https://github.com/uutils/coreutils/issues/10020 · CVE-2026-35341

来源与许可

本页自动同步 GitHub Advisory Database 的公开数据，并保留上游原文供核验；不宣称原创分析。数据许可：CC-BY-4.0。