How severe is GHSA-978j-88f3-p5j3?

No CVSS score has been assigned to GHSA-978j-88f3-p5j3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-978j-88f3-p5j3?

GHSA-978j-88f3-p5j3 affects the following packages: shamir (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-978j-88f3-p5j3?

Update shamir to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-978j-88f3-p5j3 is resolved across your whole dependency graph.

How do I detect GHSA-978j-88f3-p5j3 in my crates.io dependencies?

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

How do I mitigate GHSA-978j-88f3-p5j3 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-978j-88f3-p5j3?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-978j-88f3-p5j3 can be triaged on real exposure rather than presence alone.

Is GHSA-978j-88f3-p5j3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-978j-88f3-p5j3 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-978j-88f3-p5j3 published, and has it been updated?

GHSA-978j-88f3-p5j3 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

Not in CISA KEV

GHSA-978j-88f3-p5j3 — shamir

GHSA-978j-88f3-p5j3 is a security vulnerability in shamir. A fix is available for shamir — see the affected versions and patch details below.

Threshold value is ignored (all shares are n=3)

Also known asRUSTSEC-2020-0160

Published

Jun 17, 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

🦀shamir

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 did not properly calculate secret shares requirements.

This reduces the security of the algorithm by restricting the crate to always using a threshold value of three, rather than a configurable limit.

The flaw was corrected by correctly configuring the threshold.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`shamir`	all versions	2.0.0`cargo update -p shamir --precise 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 shamir, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shamir to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-978j-88f3-p5j3 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-978j-88f3-p5j3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-978j-88f3-p5j3. 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 did not properly calculate secret shares requirements. This reduces the security of the algorithm by restricting the crate to always using a threshold value of three, rather than a configurable limit. The flaw was corrected by correctly configuring the threshold.

O3 Security · Impact-Aware SCA

Is GHSA-978j-88f3-p5j3 in your dependencies?

O3 Security finds GHSA-978j-88f3-p5j3 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