# RUSTSEC-2017-0008: `serial` crate is unmaintained

> The serial crate is unmaintained, posing supply chain risks; developers should migrate to maintained alternatives like serial2 or tokio-serial.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 2 Jul 2017

## What is RUSTSEC-2017-0008?

RUSTSEC-2017-0008 is a vulnerability in serial, published on 2 Jul 2017. 

### Official description

The [`serial`](https://crates.io/crates/serial) crate is no longer maintained.

Last release was on 2017-07-02.

## Possible alternatives

Consider using an alternative, for instance the blocking librarys:

- [serial2](https://crates.io/crates/serial2)
- [serialport](https://crates.io/crates/serialport)

or async alternatives:

- [mio-serial](https://crates.io/crates/mio-serial)
- [tokio-serial](https://crates.io/crates/tokio-serial)

## Which versions are affected by RUSTSEC-2017-0008?

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


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

## How do I fix RUSTSEC-2017-0008?

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

## Is RUSTSEC-2017-0008 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2017-0008 and fix it if it is affected.

What it is: RUSTSEC-2017-0008 is a vulnerability in serial, published on 2 Jul 2017. 
Exploitation: There is no known exploitation of RUSTSEC-2017-0008 in the wild and no public exploit code.

Affected packages and fixed versions:
- serial (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-2017-0008/ (Markdown: https://insights.sbomify.com/RUSTSEC-2017-0008/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2017-0008

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