RUSTSEC-2020-0159: Potential segfault in `localtime_r` invocations
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
No source file, dependency manifest, or test is named in the issue. Start by checking the repository's Rust dependency declarations for chrono and compare the resolved version with the RUSTSEC-2020-0159 advisory; done means the vulnerable dependency is addressed and relevant checks pass.
Written by the indexing model from the issue text.
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.
- Dominant language
- Rust
- Stars
- 28
- Forks
- 8
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from stackabletech/kafka-operator
-
type/bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
stackabletech/kafka-operator#955 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/kafka-operator#941 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/kafka-operator#874 ·
Maintainers usually reply within 1 day
-
Kafka 4.xMay be free again @razvan claimed this 350 days ago, and no pull request is open. Openrefinement-needed
stackabletech/kafka-operator#870 · 5 comments · 2 assignees ·
Maintainers usually reply within 1 day
-
customer-request
Difficulty 4/5 3-5 days Newbie friendliness 30/100
stackabletech/kafka-operator#859 ·
Maintainers usually reply within 1 day
All issues in stackabletech/kafka-operator
Similar issues
-
backend::vllm diffusion multimodal
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lambdaclass/ethrex#7329 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
shadowsocks/shadowsocks-rust#2186 · 1 comment ·
-
C-bug S-awaiting-triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
juspay/hyperswitch#14479 ·
Maintainers usually reply within 1 day