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.

Sign up for GitHub

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

Jump to bottom

RUSTSEC-2020-0159: Potential segfault in localtime_r invocations #660

Closed
github-actions bot opened this issue Oct 19, 2021 · 2 comments
Closed

RUSTSEC-2020-0159: Potential segfault in localtime_r invocations #660

github-actions bot opened this issue Oct 19, 2021 · 2 comments
Labels
invalid rejected as a valid issue security related to advisories or CVEs

Comments

@github-actions
Copy link
Contributor

Potential segfault in localtime_r invocations

Details
Package chrono
Version 0.4.19
URL chronotope/chrono#499
Date 2020-11-10

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

See advisory page for additional details.
@clux
Copy link
Member

clux commented Oct 19, 2021

see #650

@clux clux added security related to advisories or CVEs invalid rejected as a valid issue labels Dec 4, 2021
@olix0r olix0r mentioned this issue Jan 19, 2022
Open
@clux
Copy link
Member

clux commented Aug 8, 2022

Going to close this now as chrono 0.4.20 is out and requires no action on us to be propagated.

@clux clux closed this as completed Aug 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
invalid rejected as a valid issue security related to advisories or CVEs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@clux