GHSA-58XC-HPVQ-8473

Vulnerability from github – Published: 2025-05-06 20:00 – Updated: 2025-05-06 20:00
VLAI?
Summary
Redox UEFI Safe API can cause heap-buffer-overflow
Details

ffi::nstr() should be marked unsafe, since a pointer to a buffer without a trailing 0 value will cause a heap buffer overflow.

Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "crates.io",
        "name": "redox_uefi_std"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.1.8"
            },
            {
              "fixed": "0.1.14"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-122"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-05-06T20:00:17Z",
    "nvd_published_at": null,
    "severity": "LOW"
  },
  "details": "ffi::nstr() should be marked unsafe, since a pointer to a buffer without a trailing 0 value will cause a heap buffer overflow.",
  "id": "GHSA-58xc-hpvq-8473",
  "modified": "2025-05-06T20:00:17Z",
  "published": "2025-05-06T20:00:17Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://gitlab.redox-os.org/redox-os/uefi"
    },
    {
      "type": "WEB",
      "url": "https://gitlab.redox-os.org/redox-os/uefi/-/commit/b711d47e815665b0ec8949e39292ad8e3fdd0756"
    },
    {
      "type": "WEB",
      "url": "https://rustsec.org/advisories/RUSTSEC-2025-0032.html"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "Redox UEFI Safe API can cause heap-buffer-overflow"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.



Detection rules are retrieved from Rulezet.