Summary
Post-Quantum Secure Feldman's Verifiable Secret Sharing has Inadequate Fault Injection Countermeasures in secureredundantexecution
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
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-29779? CVE-2025-29779 is a medium-severity security vulnerability in PostQuantum-Feldman-VSS (pip), affecting versions <= 0.8.0b2. No fixed version is listed yet.
- Which versions of PostQuantum-Feldman-VSS are affected by CVE-2025-29779? PostQuantum-Feldman-VSS (pip) versions <= 0.8.0b2 is affected.
- Is there a fix for CVE-2025-29779? No fixed version is listed for CVE-2025-29779 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is CVE-2025-29779 exploitable, and should I be worried? Whether CVE-2025-29779 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-29779 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.