cargo package report

Is memoffset safe?

2 known vulnerabilities, worst severity HIGH.

cvss

7.5

how bad it is if exploited, out of 10

epss

1.8%

chance of exploitation in the next 30 days

xyz score

3.4

CyberXYZ composite, out of 10

fig. 01 — GHSA-rh89-x75f-rh3c, the advisory selected below

// advisories

GHSA-rh89-x75f-rh3c

HIGHCVE-2019-15553

Affected versions of this crate caused traps and/or memory unsafety by zero-initializing references. They also could lead to uninitialized memory being dropped if the field for which the offset is requested was behind a deref coercion, and that deref coercion caused a panic. The flaw was corrected by using MaybeUninit.

Affected: < 0.5.0
Fixed in: 0.5.0
Weakness: CWE-908
Published: 2021-08-25
Source: github

GHSA NVD MITRE reference reference

// dependencies

0 direct

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so cargo packages are not covered.

Checked 2026-09-22 at 01:39 UTC. The most recent advisory here was published 2023-06-21. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Is memoffset safe? cargo package security report | CyberXYZ