stackabletech / stackabletech/nifi-operator
RUSTSEC-2020-0159: Potential segfault in `localtime_r` invocations
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 48
- Forks
- 12
- Avg merge
- 11h 26m
- Merged PRs (30d)
- 10
Description
Potential segfault in
localtime_rinvocations
| Details | |
|---|---|
| Package | chrono |
| Version | 0.4.19 |
| URL | https://github.com/chronotope/chrono/issues/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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked RustSec advisory and the chrono issue referenced in the report. Then locate where this repository declares or uses chrono; no file, test, or entry point is named here. Done means the reported RUSTSEC-2020-0159 exposure has been addressed and the relevant project checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100