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

Security advisory: please release with upgraded time dependency #709

Closed
getreu opened this issue Jun 13, 2022 · 4 comments
Closed

Security advisory: please release with upgraded time dependency #709

getreu opened this issue Jun 13, 2022 · 4 comments

Comments

@getreu
Copy link

getreu commented Jun 13, 2022

Solution: Solution: Upgrade time to >=0.2.23

See dependency tree below cargo audit:

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
Dependency tree:
time 0.1.44
└── chrono 0.4.19
    ├── tp-note 1.17.0
    ├── tera 1.15.0
    │   └── tp-note 1.17.0
    └── chrono-tz 0.6.1
        └── tera 1.15.0
@djc
Copy link
Contributor

djc commented Jun 13, 2022

See #602.

@cristicbz
Copy link

@djc The currently released version also calls locatime_r directly (https://docs.rs/chrono/0.4.19/src/chrono/sys/unix.rs.html#84), so even without the oldtime feature, I think this is still affected by the CVE---is there a blocker to cutting a new release without the localtime_r call?

If there's interest, I could try to backport minimal changes to 0.4.19 to remove the localtime_r call?

@djc
Copy link
Contributor

djc commented Jun 21, 2022

See #602.

@djc djc closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2022
@djc
Copy link
Contributor

djc commented Jun 21, 2022

Sorry, I meant #674.

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

No branches or pull requests

3 participants