# RUSTSEC-2024-0395: The maintainer of chrono-english is unresponsive

> Unmaintained Rust library causes compilation failures with newer dependencies, requiring migration to a maintained fork.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2024

## What is RUSTSEC-2024-0395?

RUSTSEC-2024-0395 is a vulnerability in chrono-english, published on 24 Jun 2024. 

### Official description

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.

## Which versions are affected by RUSTSEC-2024-0395?

1 open source package ship an affected version, including chrono-english.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `chrono-english` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2024-0395?

No fix has been published for RUSTSEC-2024-0395 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2024-0395 being exploited?

There is no known exploitation of RUSTSEC-2024-0395 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2024-0395 and fix it if it is affected.

What it is: RUSTSEC-2024-0395 is a vulnerability in chrono-english, published on 24 Jun 2024. 
Exploitation: There is no known exploitation of RUSTSEC-2024-0395 in the wild and no public exploit code.

Affected packages and fixed versions:
- chrono-english (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2024-0395/ (Markdown: https://insights.sbomify.com/RUSTSEC-2024-0395/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2024-0395

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2024-0395/
Summaries are generated and may contain mistakes; the official description above is the record.