Repository navigation
Replies: 2 comments
|
still a lot of advisories not imported to rustsec weird |
0 replies
|
https://github.com/RustSec/advisory-db/blob/main/CONTRIBUTING.md |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi, thanks for publishing all the advisories from the audits. While comparing advisory databases for Rust crates, we found two gaps that affect how tools report uutils. You may want to fix them, or you may prefer to leave them alone, so we're asking before filing anything.
1. GitHub's reviewed copies of eight CVEs miss 0.9.0. For 21 CVEs, GitHub keeps two records: the reviewed one from April, which names
coreutilsand is what Dependabot and OSV use, and your own advisory, which names theuu_*crate. For eight of them, the reviewed record says "last affected 0.8.0", while your advisory says 0.9.0 is also affected and 0.10.0 fixes it:Another contributor has filed corrections for the first three (github/advisory-database#10664, #10665 and #10666, open since 2026-10-25). The other five have none yet. Eight more reviewed records (cp, mv, nohup, chroot) have the right versions but list no patched version.
2. Nothing from 2026 is in RustSec. cargo-audit and cargo-deny read RustSec, not GitHub. Your advisories name the per-tool crates, and those crates are used directly: for example, brush-coreutils-builtins 0.1.0 requires
uu_cp ^0.8.0. Its users get no alert from either tool.The full table, with how each row was checked: https://github.com/munimtechnologies/advisory-import-census/blob/main/docs/notes/uutils-advisory-ranges-2026-11-12.md
Questions:
MV2, Munim, Inc. (mv2@munimtech.com). This research and post were made with AI agents working in MV2's name.
All reactions