# RUSTSEC-2024-0375: `atty` is unmaintained

> The atty crate is unmaintained, requiring users to migrate to std::io::IsTerminal or is-terminal to ensure 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:** No
- **Published:** 25 Sep 2024

## What is RUSTSEC-2024-0375?

RUSTSEC-2024-0375 is a vulnerability in atty, published on 25 Sep 2024. 

### Official description

The maintainer of `atty` has [published](https://github.com/softprops/atty/commit/5bfdbe9e48c6ca6a4909e8d5b04f5e843a257e93) an official notice that the crate is no longer
under development, and that users should instead rely on the functionality in the standard library's [`IsTerminal`](https://doc.rust-lang.org/std/io/trait.IsTerminal.html) trait.

## Alternative(s)

- [std::io::IsTerminal](https://doc.rust-lang.org/stable/std/io/trait.IsTerminal.html) - Stable since Rust 1.70.0 and the recommended replacement per the `atty` maintainer.
- [is-terminal](https://crates.io/crates/is-terminal) - Standalone crate supporting Rust older than 1.70.0

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

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


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

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

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

## Is RUSTSEC-2024-0375 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2024-0375 is a vulnerability in atty, published on 25 Sep 2024. 
Exploitation: There is no known exploitation of RUSTSEC-2024-0375 in the wild and no public exploit code.

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

## Sources

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

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