Skip to content

Commit d7dad3f

Browse files
committed
Add chrono advisory for chrono#499 (localtime_r)
This is an advisory similar to `RUSTSEC-2020-0071` impacting usages of `localtime_r` within `chrono` itself, since the API is used in a cross-thread manner in an unsound way.
1 parent 5335769 commit d7dad3f

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

crates/chrono/RUSTSEC-0000-0000.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
```toml
2+
[advisory]
3+
id = "RUSTSEC-0000-0000"
4+
package = "chrono"
5+
date = "2020-11-10"
6+
url = "https://github.com/chronotope/chrono/issues/499"
7+
categories = ["code-execution", "memory-corruption"]
8+
keywords = ["segfault"]
9+
related = ["CVE-2020-26235", "RUSTSEC-2020-0071"]
10+
11+
[versions]
12+
patched = []
13+
```
14+
15+
# Potential segfault in `localtime_r` invocations
16+
17+
### Impact
18+
19+
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.
20+
21+
### Workarounds
22+
23+
No workarounds are known.
24+
25+
### References
26+
27+
- [time-rs/time#293](https://github.com/time-rs/time/issues/293)

0 commit comments

Comments
 (0)