# GHSA-2qv5-7mw5-j3cg: spin-rs initialisation failure in `Once::try_call_once` can lead to undefined behaviour for other initialisers

> Concurrent initialization failures in spin-rs can cause undefined behavior, potentially allowing arbitrary code execution in applications using the library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Mar 2023
- **Also known as:** RUSTSEC-2023-0031

## What is GHSA-2qv5-7mw5-j3cg?

GHSA-2qv5-7mw5-j3cg is a vulnerability in spin, published on 31 Mar 2023. 

### Official description

`Once::try_call_once` is unsound if invoked more than once concurrently and any call fails to initialise successfully.

## Which versions are affected by GHSA-2qv5-7mw5-j3cg?

3 open source packages ship an affected version, including spin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `spin` | crates.io | From 0.9.3 | 0.9.8 |
| `spin` | crates.io | From 0.9.3 | 0.9.8 |
| `spin` | crates.io | From 0.9.3 | 0.9.8 |

## How do I fix GHSA-2qv5-7mw5-j3cg?

Upgrade spin to 0.9.8 or later.

## Is GHSA-2qv5-7mw5-j3cg being exploited?

There is no known exploitation of GHSA-2qv5-7mw5-j3cg in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2qv5-7mw5-j3cg and fix it if it is affected.

What it is: GHSA-2qv5-7mw5-j3cg is a vulnerability in spin, published on 31 Mar 2023. 
Exploitation: There is no known exploitation of GHSA-2qv5-7mw5-j3cg in the wild and no public exploit code.

Affected packages and fixed versions:
- spin (crates.io): affected from 0.9.3; fixed in 0.9.8
- spin (crates.io): affected from 0.9.3; fixed in 0.9.8
- spin (crates.io): affected from 0.9.3; fixed in 0.9.8

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/GHSA-2qv5-7mw5-j3cg/ (Markdown: https://insights.sbomify.com/GHSA-2qv5-7mw5-j3cg/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2qv5-7mw5-j3cg

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2qv5-7mw5-j3cg/
Summaries are generated and may contain mistakes; the official description above is the record.