GHSA-8frv-q972-9rq5 — cggmp21
Fix: LFDT-Lockness/cggmp21@9d98157GHSA-8frv-q972-9rq5 is a Broken Cryptographic Algorithm vulnerability in cggmp21. A fix is available for cggmp21 — see the affected versions and patch details below.
cggmp24 and cggmp21 are vulnerable to signature forgery through altered presignatures
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-8frv-q972-9rq5.
EPSS Exploitation Probability
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.
Real-World Exposure
cggmp21🦀cggmp24Real-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
Impact
This attack is against presignatures used in very specific context:
- Presignatures + HD wallets derivation: security level reduces to 85 bits
Previously users could generate a presignature, and then choose a HD derivation path while issuing a partial signature viaPresignature::set_derivation_path, which is malleable to attack that reduces target security level. To mitigate, this method has been removed from API. - Presignatures + "raw signing" (when signer signs a hash without knowing an original message): results into signature forgery attack
Previously, users were able to configurePresignature::issue_partial_signaturewith hashed message without ever providing original mesage. In new API, this method only accepts digests for which original message has been observed.
Patches
cggmp24 v0.7.0-alpha.2 release contains API changes that make it impossible to use presignatures in contexts in which it reduces security. Follow migration guidelines to upgrade.
Workarounds
Users can continue using un-patched versions of library as long as they don't use presignatures in said scenarios where it weakens system security. To be sure, migrate to patched version that excludes presignatures from being used in such scenarios.
References
Read this blog post to learn more.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | cggmp21 | all versions | No fix |
| 🦀crates.io | cggmp24 | all versions | 0.7.0-alpha.2cargo update -p cggmp24 --precise 0.7.0-alpha.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cggmp21, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of cggmp21 has shipped for GHSA-8frv-q972-9rq5 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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-8frv-q972-9rq5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8frv-q972-9rq5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8frv-q972-9rq5 in your dependencies?
O3 Security finds GHSA-8frv-q972-9rq5 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.