# RUSTSEC-2025-0030: totally-safe-transmute allows transmuting any type to any other type in safe Rust > The totally-safe-transmute crate allows unsafe memory manipulation via /proc/self/mem, enabling arbitrary code execution or privilege escalation in safe Rust. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Not stated - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 10 Feb 2025 ## What is RUSTSEC-2025-0030? RUSTSEC-2025-0030 is a memory corruption vulnerability in totally-safe-transmute, published on 10 Feb 2025. ### Official description This crate is a toy and should never be used. It showcases a known soundness issue (https://github.com/rust-lang/rust/issues/32670) that will never get fixed. In short, Linux provides a file called `/proc/self/mem` which can be used by a program to modify its own memory. This library modifies an enum variant number by accessing its own memory as a file to effectively transmute a variable. See also ## Which versions are affected by RUSTSEC-2025-0030? 1 open source package ship an affected version, including totally-safe-transmute. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `totally-safe-transmute` | crates.io | From 0.0.0-0 | None | ## How do I fix RUSTSEC-2025-0030? No fix has been published for RUSTSEC-2025-0030 yet. Limit exposure of the affected software until one is available. ## Is RUSTSEC-2025-0030 being exploited? There is no known exploitation of RUSTSEC-2025-0030 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for RUSTSEC-2025-0030 and fix it if it is affected. What it is: RUSTSEC-2025-0030 is a memory corruption vulnerability in totally-safe-transmute, published on 10 Feb 2025. Exploitation: There is no known exploitation of RUSTSEC-2025-0030 in the wild and no public exploit code. Affected packages and fixed versions: - totally-safe-transmute (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-0030/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0030/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/RUSTSEC-2025-0030 --- From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2025-0030/ Summaries are generated and may contain mistakes; the official description above is the record.