How severe is GHSA-mcrf-7hf9-f6q5?

No CVSS score has been assigned to GHSA-mcrf-7hf9-f6q5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mcrf-7hf9-f6q5?

GHSA-mcrf-7hf9-f6q5 affects the following packages: rmpv (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-mcrf-7hf9-f6q5?

Update rmpv to 0.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mcrf-7hf9-f6q5 is resolved across your whole dependency graph.

How do I detect GHSA-mcrf-7hf9-f6q5 in my crates.io dependencies?

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

How do I mitigate GHSA-mcrf-7hf9-f6q5 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-mcrf-7hf9-f6q5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mcrf-7hf9-f6q5 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.

When was GHSA-mcrf-7hf9-f6q5 published, and has it been updated?

GHSA-mcrf-7hf9-f6q5 was published on August 25, 2021 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

Unchecked vector pre-allocationGHSA-mcrf-7hf9-f6q5

GHSA-mcrf-7hf9-f6q5 is a remote code execution vulnerability in rmpv. A fix is available for rmpv — see the affected versions and patch details below.

Also known asRUSTSEC-2017-0006

Published

Aug 25, 2021

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀rmpv

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

Affected versions of this crate pre-allocate memory on deserializing raw buffers without checking whether there is sufficient data available. This allows an attacker to do denial-of-service attacks by sending small msgpack messages that allocate gigabytes of memory.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`rmpv`	all versions	0.4.2`cargo update -p rmpv --precise 0.4.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rmpv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rmpv to 0.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mcrf-7hf9-f6q5 is resolved across your whole dependency graph.
Workarounds
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

O3 Security · Impact-Aware SCA

Is GHSA-mcrf-7hf9-f6q5 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works