# RUSTSEC-2018-0015: term is looking for a new maintainer

> The term crate is unmaintained, requiring users to switch to maintained alternatives like crossterm or termcolor.

- **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:** 19 Nov 2018

## What is RUSTSEC-2018-0015?

RUSTSEC-2018-0015 is a vulnerability in term, published on 19 Nov 2018. 

### Official description

The author of the `term` crate does not have time to maintain it and is looking
for a new maintainer.

Some maintained alternatives you can potentially switch to instead, depending
on your needs:

- [`crossterm`](https://github.com/crossterm-rs/crossterm)
- [`termcolor`](https://crates.io/crates/termcolor)
- [`yansi`](https://crates.io/crates/yansi)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `term` | crates.io | From 0.0.0-0 | 0.6.2-0 |

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

Upgrade term to 0.6.2-0 or later.

## Is RUSTSEC-2018-0015 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2018-0015 is a vulnerability in term, published on 19 Nov 2018. 
Exploitation: There is no known exploitation of RUSTSEC-2018-0015 in the wild and no public exploit code.

Affected packages and fixed versions:
- term (crates.io): affected from 0.0.0-0; fixed in 0.6.2-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-0015/ (Markdown: https://insights.sbomify.com/RUSTSEC-2018-0015/index.md)
```

## Sources

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

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