CVE-2025-29779 — postquantum-feldman-vss
CVE-2025-29779 is a CWE-1240 vulnerability in postquantum-feldman-vss. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Post-Quantum Secure Feldman's Verifiable Secret Sharing has Inadequate Fault Injection Countermeasures in `secure_redundant_execution`
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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 CVE-2025-29779.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
postquantum-feldman-vssReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Description:
The secure_redundant_execution function in feldman_vss.py attempts to mitigate fault injection attacks by executing a function multiple times and comparing results. However, several critical weaknesses exist:
- Python's execution environment cannot guarantee true isolation between redundant executions
- The constant-time comparison implementation in Python is subject to timing variations
- The randomized execution order and timing provide insufficient protection against sophisticated fault attacks
- The error handling may leak timing information about partial execution results
These limitations make the protection ineffective against targeted fault injection attacks, especially from attackers with physical access to the hardware.
Impact:
A successful fault injection attack could allow an attacker to:
- Bypass the redundancy check mechanisms
- Extract secret polynomial coefficients during share generation or verification
- Force the acceptance of invalid shares during verification
- Manipulate the commitment verification process to accept fraudulent commitments
This undermines the core security guarantees of the Verifiable Secret Sharing scheme.
References:
- File:
feldman_vss.py - Function:
secure_redundant_execution - Fault Attacks - Wikipedia article on fault attacks.
- Bar-El, H., et al. "The Sorcerer's Apprentice Guide to Fault Attacks" - https://eprint.iacr.org/2004/100.pdf
- CWE-1279: https://cwe.mitre.org/data/definitions/1279.html
- NIST SP 800-90B section on implementation validation
Remediation:
Long-term remediation requires reimplementing the security-critical functions in a lower-level language like Rust.
Short-term mitigations:
- Deploy the software in environments with physical security controls
- Increase the redundancy count (from 5 to a higher number) by modifying the source code
- Add external verification of cryptographic operations when possible
- Consider using hardware security modules (HSMs) for key operations
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | postquantum-feldman-vss | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for postquantum-feldman-vss, 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 postquantum-feldman-vss for CVE-2025-29779. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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.
Frequently Asked Questions
Is CVE-2025-29779 in your dependencies?
Find it across PyPI, including transitive dependencies.