# RUSTSEC-2021-0096: spirv_headers is unmaintained, use spirv instead

> The spirv_headers crate is unmaintained, requiring users to switch to the spirv crate for parsing SPIR-V files.

- **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:** 16 Aug 2021

## What is RUSTSEC-2021-0096?

RUSTSEC-2021-0096 is a vulnerability in spirv_headers, published on 16 Aug 2021. 

### Official description

Because of versioning issues; the `spirv_headers` crate is unmaintained. Use [spirv](https://crates.io/crates/spirv)
for parsing spirv files.

## Which versions are affected by RUSTSEC-2021-0096?

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


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

## How do I fix RUSTSEC-2021-0096?

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

## Is RUSTSEC-2021-0096 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2021-0096 and fix it if it is affected.

What it is: RUSTSEC-2021-0096 is a vulnerability in spirv_headers, published on 16 Aug 2021. 
Exploitation: There is no known exploitation of RUSTSEC-2021-0096 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2021-0096

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