How severe is GHSA-pmcv-mgcf-rvxg?

No CVSS score has been assigned to GHSA-pmcv-mgcf-rvxg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pmcv-mgcf-rvxg?

GHSA-pmcv-mgcf-rvxg affects the following packages: crypto2 (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-pmcv-mgcf-rvxg?

The records we use list no patched version of crypto2 for GHSA-pmcv-mgcf-rvxg. 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-pmcv-mgcf-rvxg in my crates.io dependencies?

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

How do I mitigate GHSA-pmcv-mgcf-rvxg if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-pmcv-mgcf-rvxg actively exploited in the wild?

No public exploit code has been indexed for GHSA-pmcv-mgcf-rvxg 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-pmcv-mgcf-rvxg?

GHSA-pmcv-mgcf-rvxg has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th 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-pmcv-mgcf-rvxg?

GHSA-pmcv-mgcf-rvxg is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-pmcv-mgcf-rvxg published, and has it been updated?

GHSA-pmcv-mgcf-rvxg 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

Non-aligned u32 read in Chacha20 encryption and decryptionGHSA-pmcv-mgcf-rvxg

GHSA-pmcv-mgcf-rvxg is a Buffer Overflow vulnerability in crypto2. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2021-45709 GHSA-9hfg-pxr6-q4vpRUSTSEC-2021-0121

Published

Jun 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🦀crypto2

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

The implementation does not enforce alignment requirements on input slices while incorrectly assuming 4-byte alignment through an unsafe call to std::slice::from_raw_parts_mut, which breaks the contract and introduces undefined behavior.

This affects Chacha20 encryption and decryption in crypto2.

Affected Packages

1 total

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

Affected Products

1 product · 1 configurations

Application

crypto2crypto2_project

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for crypto2, 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 crypto2 for GHSA-pmcv-mgcf-rvxg. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

The implementation does not enforce alignment requirements on input slices while incorrectly assuming 4-byte alignment through an unsafe call to `std::slice::from_raw_parts_mut`, which breaks the contract and introduces undefined behavior. This affects Chacha20 encryption and decryption in crypto2.

O3 Security · Impact-Aware SCA

Is GHSA-pmcv-mgcf-rvxg in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works