# RUSTSEC-2022-0056: clipboard is Unmaintained

> The clipboard library is unmaintained and abandoned, posing supply chain risks due to unpatched dependencies and potential maintainer account takeover.

- **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 Jun 2022

## What is RUSTSEC-2022-0056?

RUSTSEC-2022-0056 is a vulnerability in clipboard, published on 25 Jun 2022. 

### Official description

Last release was almost 4 years ago and the repository with outstanding issues and pull requests seems to be abandoned by the maintainer.

In addition the sole maintainer account may be abandoned that may represent account takeover risk.

Current outstanding issues include vulnerable dependencies that all together may mean that security issues may not be addressed now or in the future.

## Possible Alternative(s)

The below list has not been vetted in any way and may or may not contain alternatives;

- [`arboard`](https://crates.io/crates/arboard)
- [`clipboard-win`](https://crates.io/crates/clipboard-win) (Windows only)
- [`copy-pasta`](https://crates.io/crates/copypasta)
- [`x11-clipboard`](https://crates.io/crates/x11-clipboard) (Linux/BSD only)

## Which versions are affected by RUSTSEC-2022-0056?

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


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

## How do I fix RUSTSEC-2022-0056?

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

## Is RUSTSEC-2022-0056 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2022-0056 and fix it if it is affected.

What it is: RUSTSEC-2022-0056 is a vulnerability in clipboard, published on 25 Jun 2022. 
Exploitation: There is no known exploitation of RUSTSEC-2022-0056 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2022-0056

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