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-0159: Potential segfault in localtime_r invocations #47

Closed
github-actions bot opened this issue Apr 12, 2022 · 0 comments · Fixed by #49
Closed

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

github-actions bot opened this issue Apr 12, 2022 · 0 comments · Fixed by #49

Comments

@github-actions
Copy link

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.

mrl5 added a commit that referenced this issue Apr 12, 2022
@mrl5 mrl5 closed this as completed in #49 Apr 12, 2022
mrl5 added a commit that referenced this issue Apr 12, 2022
fix: cargo audit fix - drop chrono dependency [#47][#48]
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.

0 participants