How severe is GHSA-mpg5-fvwp-42m2?

No CVSS score has been assigned to GHSA-mpg5-fvwp-42m2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mpg5-fvwp-42m2?

GHSA-mpg5-fvwp-42m2 affects the following packages: dashmap (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-mpg5-fvwp-42m2?

Update dashmap to 5.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mpg5-fvwp-42m2 is resolved across your whole dependency graph.

How do I detect GHSA-mpg5-fvwp-42m2 in my crates.io dependencies?

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

How do I mitigate GHSA-mpg5-fvwp-42m2 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-mpg5-fvwp-42m2?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mpg5-fvwp-42m2 can be triaged on real exposure rather than presence alone.

Is GHSA-mpg5-fvwp-42m2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mpg5-fvwp-42m2 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-mpg5-fvwp-42m2 published, and has it been updated?

GHSA-mpg5-fvwp-42m2 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

GHSA-mpg5-fvwp-42m2 — dashmap

GHSA-mpg5-fvwp-42m2 is a security vulnerability in dashmap. A fix is available for dashmap — see the affected versions and patch details below.

Unsoundness in `dashmap` references

Also known asRUSTSEC-2022-0002

Published

Jun 16, 2022

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

🦀dashmap

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

Reference returned by some methods of Ref (and similar types) may outlive the Ref and escape the lock. This causes undefined behavior and may result in a segfault.

More information in dashmap#167 issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`dashmap`	≥ 5.0.0&&< 5.1.0	5.1.0`cargo update -p dashmap --precise 5.1.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dashmap, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dashmap to 5.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mpg5-fvwp-42m2 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mpg5-fvwp-42m2 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mpg5-fvwp-42m2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Reference returned by some methods of `Ref` (and similar types) may outlive the `Ref` and escape the lock. This causes undefined behavior and may result in a segfault. More information in [`dashmap#167`](https://github.com/xacrimon/dashmap/issues/167) issue.

O3 Security · Impact-Aware SCA

Is GHSA-mpg5-fvwp-42m2 in your dependencies?

O3 Security finds GHSA-mpg5-fvwp-42m2 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works