Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-r8gc-qc2c-c7vh

MediumCVSS 5.4 / 10
Published Mar 14, 2025·Last modified Mar 30, 2025
Affected Components(0)

No affected components available

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:

  1. Python's execution environment cannot guarantee true isolation between redundant executions
  2. The constant-time comparison implementation in Python is subject to timing variations
  3. The randomized execution order and timing provide insufficient protection against sophisticated fault attacks
  4. 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:

  1. Bypass the redundancy check mechanisms
  2. Extract secret polynomial coefficients during share generation or verification
  3. Force the acceptance of invalid shares during verification
  4. 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:

  1. Deploy the software in environments with physical security controls
  2. Increase the redundancy count (from 5 to a higher number) by modifying the source code
  3. Add external verification of cryptographic operations when possible
  4. Consider using hardware security modules (HSMs) for key operations
Risk Scores
Base Score
5.4

The vulnerability requires physical access to the device to be exploited. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability.

Threat Intelligence
2.0

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
0.18%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Related Vulnerabilities

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard