# RUSTSEC-2016-0006: `cassandra` crate is unmaintained; use `cassandra-cpp` instead

> The cassandra crate is unmaintained, posing supply chain risks; developers should migrate to the maintained cassandra-cpp fork.

- **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:** 15 Dec 2016

## What is RUSTSEC-2016-0006?

RUSTSEC-2016-0006 is a vulnerability in cassandra, published on 15 Dec 2016. 

### Official description

The `cassandra` crate has not seen a release since December 2016, and its author
is unresponsive.

The `cassandra-cpp` crate is a maintained fork:

https://github.com/Metaswitch/cassandra-rs

## Which versions are affected by RUSTSEC-2016-0006?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cassandra` | crates.io | From 0.0.0-0 | 0.8.2-0 |

## How do I fix RUSTSEC-2016-0006?

Upgrade cassandra to 0.8.2-0 or later.

## Is RUSTSEC-2016-0006 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2016-0006 and fix it if it is affected.

What it is: RUSTSEC-2016-0006 is a vulnerability in cassandra, published on 15 Dec 2016. 
Exploitation: There is no known exploitation of RUSTSEC-2016-0006 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2016-0006

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