# RUSTSEC-2019-0024: Test advisory with associated example crate

> This is a test advisory for an empty example crate used to verify RustSec tooling, with no actual security impact.

- **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:** 8 Oct 2019

## What is RUSTSEC-2019-0024?

RUSTSEC-2019-0024 is a vulnerability in rustsec-example-crate, published on 8 Oct 2019. 

### Official description

This is a test advisory useful for verifying RustSec tooling and vulnerability
detection pipelines are working correctly. Aside from the fact that it is filed
against an example crate, it is otherwise considered by the Advisory Database
itself to be a normal security advisory.

It's filed against `rustsec-example-crate`, an otherwise completely empty crate
with no functionality or code, which has three releases:

- [v0.0.0] - *unaffected* by this advisory (but *yanked* from crates.io)
- [v0.0.1] - *vulnerable* according to this advisory
- [v1.0.0] - *patched* by this advisory

[v0.0.0]: https://crates.io/crates/rustsec-example-crate/0.0.0
[v0.0.1]: https://crates.io/crates/rustsec-example-crate/0.0.1
[v1.0.0]: https://crates.io/crates/rustsec-example-crate/1.0.0

## Which versions are affected by RUSTSEC-2019-0024?

1 open source package ship an affected version, including rustsec-example-crate.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rustsec-example-crate` | crates.io | From 0.0.1 | 1.0.0 |

## How do I fix RUSTSEC-2019-0024?

Upgrade rustsec-example-crate to 1.0.0 or later.

## Is RUSTSEC-2019-0024 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2019-0024 and fix it if it is affected.

What it is: RUSTSEC-2019-0024 is a vulnerability in rustsec-example-crate, published on 8 Oct 2019. 
Exploitation: There is no known exploitation of RUSTSEC-2019-0024 in the wild and no public exploit code.

Affected packages and fixed versions:
- rustsec-example-crate (crates.io): affected from 0.0.1; fixed in 1.0.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-2019-0024/ (Markdown: https://insights.sbomify.com/RUSTSEC-2019-0024/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2019-0024

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