Skip to content
Fencer Intel
no cvss —

RUSTSEC-2017-0008 json

`serial` crate is unmaintained

published 9y ago modified last yr.

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

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)

Is RUSTSEC-2017-0008 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 Fencer

Affected packages

ecosystem package affected fixed in
crates.io serial
>=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.