RUSTSEC-2024-0395 json
The maintainer of chrono-english is unresponsive
published 2y ago modified 2y ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
All versions will encounter compilation errors with a chrono version `>0.4.35`, due to backward incompatible API changes.
User conradludgade reworked the original crate and created a fork with the same API surface called [interim](https://github.com/conradludgate/interim).
The fork is better structured and passes the same test suite as chrono-english, ensuring backward compatibility.
Is RUSTSEC-2024-0395 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | chrono-english | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.