rustsec-2025-0030
Vulnerability from osv_rustsec
Published
2025-02-10 12:00
Modified
2025-05-06 20:14
Summary
totally-safe-transmute allows transmuting any type to any other type in safe Rust
Details

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 https://doc.rust-lang.org/std/os/unix/io/index.html#procselfmem-and-similar-os-features


{
  "affected": [
    {
      "database_specific": {
        "categories": [
          "memory-corruption"
        ],
        "cvss": null,
        "informational": "unsound"
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "totally-safe-transmute",
        "purl": "pkg:cargo/totally-safe-transmute"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "This crate is a toy and should never be used.\n\nIt 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.\n\nSee also \u003chttps://doc.rust-lang.org/std/os/unix/io/index.html#procselfmem-and-similar-os-features\u003e",
  "id": "RUSTSEC-2025-0030",
  "modified": "2025-05-06T20:14:30Z",
  "published": "2025-02-10T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/totally-safe-transmute"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2025-0030.html"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ben0x539/totally-safe-transmute"
    }
  ],
  "related": [],
  "severity": [],
  "summary": "totally-safe-transmute allows transmuting any type to any other type in safe Rust"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…