# RUSTSEC-2018-0014: chan is end-of-life; use crossbeam-channel instead

> The chan crate is deprecated and end-of-life, requiring migration to crossbeam-channel for continued support and security.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 31 Jul 2018

## What is RUSTSEC-2018-0014?

RUSTSEC-2018-0014 is a vulnerability in chan, published on 31 Jul 2018. 

### Official description

**`chan` has reached its end-of-life and is now deprecated.**

The intended successor of this crate is
[`crossbeam-channel`](https://github.com/crossbeam-rs/crossbeam/tree/master/crossbeam-channel).
Its API is strikingly similar, but comes with a much better `select!` macro,
better performance, a better test suite and an all-around better
implementation.

## Which versions are affected by RUSTSEC-2018-0014?

1 open source package ship an affected version, including chan.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `chan` | crates.io | From 0.0.0-0 | 0.1.24-0 |

## How do I fix RUSTSEC-2018-0014?

Upgrade chan to 0.1.24-0 or later.

## Is RUSTSEC-2018-0014 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2018-0014 and fix it if it is affected.

What it is: RUSTSEC-2018-0014 is a vulnerability in chan, published on 31 Jul 2018. 
Exploitation: There is no known exploitation of RUSTSEC-2018-0014 in the wild and no public exploit code.

Affected packages and fixed versions:
- chan (crates.io): affected from 0.0.0-0; fixed in 0.1.24-0

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-2018-0014/ (Markdown: https://insights.sbomify.com/RUSTSEC-2018-0014/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2018-0014

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