How severe is GHSA-jmwx-r3gq-qq3p?

No CVSS score has been assigned to GHSA-jmwx-r3gq-qq3p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jmwx-r3gq-qq3p?

GHSA-jmwx-r3gq-qq3p affects the following packages: vec-const (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-jmwx-r3gq-qq3p?

Update vec-const to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmwx-r3gq-qq3p is resolved across your whole dependency graph.

How do I detect GHSA-jmwx-r3gq-qq3p in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vec-const. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-jmwx-r3gq-qq3p if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-jmwx-r3gq-qq3p?

O3 pinpoints whether GHSA-jmwx-r3gq-qq3p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-jmwx-r3gq-qq3p actively exploited in the wild?

No public exploit code has been indexed for GHSA-jmwx-r3gq-qq3p 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-jmwx-r3gq-qq3p?

GHSA-jmwx-r3gq-qq3p has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 60th 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-jmwx-r3gq-qq3p?

GHSA-jmwx-r3gq-qq3p is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jmwx-r3gq-qq3p published, and has it been updated?

GHSA-jmwx-r3gq-qq3p was published on June 17, 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

GHSA-jmwx-r3gq-qq3p

vec-const attempts to construct a Vec from a pointer to a const slice

Also known asCVE-2021-45680 GHSA-x76r-966h-5qv9RUSTSEC-2021-0082

Published

Jun 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk60th percentile+0.72%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🦀vec-const

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 claimed to construct a const Vec with nonzero length and capacity, but that cannot be done because such a Vec requires a pointer from an allocator.

The implementation was later changed to just construct a std::borrow::Cow.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`vec-const`	all versions	2.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vec-const. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update vec-const to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmwx-r3gq-qq3p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jmwx-r3gq-qq3p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jmwx-r3gq-qq3p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of this crate claimed to construct a const `Vec` with nonzero length and capacity, but that cannot be done because such a `Vec` requires a pointer from an allocator. The implementation was later changed to just construct a `std::borrow::Cow`.

O3 Security · Impact-Aware SCA

Is GHSA-jmwx-r3gq-qq3p in your dependencies?

O3 detects GHSA-jmwx-r3gq-qq3p across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works