How severe is GHSA-hfxp-p695-629x?

No CVSS score has been assigned to GHSA-hfxp-p695-629x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hfxp-p695-629x?

GHSA-hfxp-p695-629x affects the following packages: abomonation (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-hfxp-p695-629x?

The records we use list no patched version of abomonation for GHSA-hfxp-p695-629x. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-hfxp-p695-629x in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for abomonation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hfxp-p695-629x if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-hfxp-p695-629x actively exploited in the wild?

No public exploit code has been indexed for GHSA-hfxp-p695-629x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hfxp-p695-629x?

GHSA-hfxp-p695-629x has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hfxp-p695-629x?

GHSA-hfxp-p695-629x is classified as CWE-668 (CWE-668). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hfxp-p695-629x published, and has it been updated?

GHSA-hfxp-p695-629x was published on June 16, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

abomonation transmutes &T to and from &[u8] without sufficient constraintsGHSA-hfxp-p695-629x

GHSA-hfxp-p695-629x is a CWE-668 vulnerability in abomonation. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2021-45708 GHSA-5vwc-r48g-wj6cRUSTSEC-2021-0120

Published

Jun 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🦀abomonation

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

This transmute is at the core of the abomonation crates. It's so easy to use it to violate alignment requirements that no test in the crate's test suite passes under miri.

The use of this transmute in serialization/deserialization also incorrectly assumes that the layout of a repr(Rust) type is stable. This transmute can also disclose both the contents of padding bytes which may be an information leak and the contents of pointers, which may be used to defeat ASLR.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`abomonation`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

abomonationabomonation_project

≤ 0.7.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for abomonation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of abomonation for GHSA-hfxp-p695-629x. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

This transmute is at the core of the abomonation crates. It's so easy to use it to violate alignment requirements that no test in the crate's test suite passes under miri. The use of this transmute in serialization/deserialization also incorrectly assumes that the layout of a repr(Rust) type is stable. This transmute can also disclose both the contents of padding bytes which may be an information leak and the contents of pointers, which may be used to defeat ASLR.

O3 Security · Impact-Aware SCA

Is GHSA-hfxp-p695-629x in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works