RUSTSEC-2025-0029 totally-safe introduces memory vulnerabilities in safe Rust
Not scored
Published
Check this codebase for RUSTSEC-2025-0029 and fix it if it is affected.
What it is: RUSTSEC-2025-0029 is a memory corruption vulnerability in totally-safe, published on 10 Feb 2025.
Exploitation: There is no known exploitation of RUSTSEC-2025-0029 in the wild and no public exploit code.
Affected packages and fixed versions:
- totally-safe (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-2025-0029/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0029/index.md)
The totally-safe crate introduces memory vulnerabilities in safe Rust, potentially allowing attackers to execute arbitrary code or escalate privileges.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is RUSTSEC-2025-0029?
RUSTSEC-2025-0029 is a memory corruption vulnerability in totally-safe, published on 10 Feb 2025.
Official description
totally-safe provides unsound APIs that exploit a soundness bug in rustc: https://github.com/rust-lang/rust/issues/25860Which versions are affected by RUSTSEC-2025-0029?
1 open source package ship an affected version, including totally-safe.
| Package | Affected | Fixed in |
|---|---|---|
totally-safe crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2025-0029?
No fix has been published for RUSTSEC-2025-0029 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is RUSTSEC-2025-0029 being exploited?
There is no known exploitation of RUSTSEC-2025-0029 in the wild and no public exploit code.