# RUSTSEC-2020-0010: tiberius is unmaintained

> The tiberius Rust library is unmaintained, requiring users to migrate to supported alternatives to avoid future security risks.

- **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:** 28 Feb 2020

## What is RUSTSEC-2020-0010?

RUSTSEC-2020-0010 is a vulnerability in tiberius, published on 28 Feb 2020. 

### Official description

The author of `tiberius` has archived the GitHub repository and left the
following note:

> I do not have the time to overhaul the library and do not intend to further
> maintain the 0.3 version relying on the old futures ecosystem.

Suggested alternatives are:

- [`odbc`](https://crates.io/crates/odbc)
- [`sqlx`](https://github.com/launchbadge/sqlx/issues/116) (forthcoming)

## Which versions are affected by RUSTSEC-2020-0010?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tiberius` | crates.io | From 0.0.0-0 | 0.3.3-0 |

## How do I fix RUSTSEC-2020-0010?

Upgrade tiberius to 0.3.3-0 or later.

## Is RUSTSEC-2020-0010 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2020-0010 and fix it if it is affected.

What it is: RUSTSEC-2020-0010 is a vulnerability in tiberius, published on 28 Feb 2020. 
Exploitation: There is no known exploitation of RUSTSEC-2020-0010 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2020-0010

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