Skip to content
New issue

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

RUSTSEC-2020-0071 chrono: Potential segfault in the time crate and #76

Closed
darnuria opened this issue Dec 11, 2022 · 1 comment · Fixed by #60
Closed

RUSTSEC-2020-0071 chrono: Potential segfault in the time crate and #76

darnuria opened this issue Dec 11, 2022 · 1 comment · Fixed by #60

Comments

@darnuria
Copy link

darnuria commented Dec 11, 2022

Hello, thanks for the crate! :)

Just launched a cargo audit on this crate and it turn out it's affected by:

I suppose the solution to these two one is to acknowledge them for now by putting them into .cargo/audit.toml
like done in trust-dns crate: trust-dns/.cargo/audit.toml and leave an issue open for now until a solution land, some work is done in chrono about theses two.

Can do a PR if you want. :)

cargo audit
    Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 473 security advisories (from /home/axel/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (170 crate dependencies)
Crate:     time
Version:   0.1.45
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
Dependency tree:
time 0.1.45
└── chrono 0.4.23
    └── mysql_common 0.29.2

error: 1 vulnerability found!
warning: 1 allowed warning found
@darnuria
Copy link
Author

darnuria commented Apr 8, 2023

Thanks! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant