async-tar and it's forks are vulnerable
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.2k
- Forks
- 544
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 45
Description
see CVE-2025-62518, GHSA-j5gw-2vrg-8fgx, and this announcement blogpost.
This should be added to the rustsec database so library maintainers will be informed about it when running cargo audit.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked CVE, GHSA advisory, and announcement to collect the affected async-tar forks and vulnerability details. Compare those details with existing RustSec database entries, then add the advisory so cargo audit reports it to affected library maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100