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 #1480

Open
github-actions bot opened this issue Oct 19, 2021 · 1 comment
Open

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

github-actions bot opened this issue Oct 19, 2021 · 1 comment
Labels
blocked Can't work on this issue because it is blocked on something out of our control priority-low

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.
@tomaka
Copy link
Contributor

tomaka commented Oct 19, 2021

Irrelevant for the wasm node.

@tomaka tomaka added the blocked Can't work on this issue because it is blocked on something out of our control label Dec 17, 2021
@tomaka tomaka mentioned this issue Feb 9, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked Can't work on this issue because it is blocked on something out of our control priority-low
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomaka