We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The result from the cargo audit command shows there is one crate (time) with a known vulnerability.
time
❯ cargo audit Fetching advisory database from `https://github.com/RustSec/advisory-db.git` Loaded 458 security advisories (from /Users/andershelsing/.cargo/advisory-db) Updating crates.io index Scanning Cargo.lock for vulnerabilities (651 crate dependencies) Crate: time Version: 0.1.44 Title: Potential segfault in the time crate Date: 2020-11-18 ID: RUSTSEC-2020-0071 URL: https://rustsec.org/advisories/RUSTSEC-2020-0071 Solution: Upgrade to >=0.2.23
Short term, triage the use of the vulnerability in the time crate, and upgrade to a version where it is patched.
The text was updated successfully, but these errors were encountered:
Looks like this was actually fixed awhile back! But I can't find the PR that did it. It was definitely before we removed the audit ignore with #7113
Sorry, something went wrong.
No branches or pull requests
Description
The result from the cargo audit command shows there is one crate (
time
) with a known vulnerability.Recommendations
Short term, triage the use of the vulnerability in the time crate, and upgrade to a version where it is patched.
The text was updated successfully, but these errors were encountered: