postquantum-feldman-vss
Affected
- introduced
0, fixed0.7.7b0(ecosystem)
Fixed versions
0.7.7b0
Fix
- Fixed version
0.7.7b0pip install --upgrade postquantum-feldman-vss==0.7.7b0
Advisory
Also known as: None
PostQuantum-Feldman-VSS'S Dependency Vulnerability in gmpy2 Leading to Interpreter Crash
Description:
PostQuantum-Feldman-VSS, a Python library implementing Feldman's Verifiable Secret Sharing scheme with post-quantum security, was vulnerable to denial-of-service attacks in versions up to and including 0.7.6b0. This vulnerability stems from the library's reliance on the gmpy2 library for arbitrary-precision arithmetic. gmpy2, in turn, depends on the GNU Multiple Precision Arithmetic Library (GMP). GMP, by design, terminates the process when it cannot allocate memory. An attacker could exploit this by providing carefully crafted inputs that cause gmpy2 to attempt to allocate extremely large amounts of memory, leading to a crash of the Python interpreter and thus a denial of service.
Vulnerability Details:
The core issue lies in the behavior of GMP (and thus, gmpy2) when memory allocation fails. Instead of raising a standard Python exception that could be caught and handled, GMP terminates the entire process. This behavior is documented in the GMP and gmpy2 documentation:
gmpy2 can crash the interpreter on memory allocation failure.)Specific operations within the PostQuantum-Feldman-VSS library that were particularly vulnerable include:
x could trigger excessive memory allocation.Mitigations in 0.8.0b2:
Version 0.8.0b2 implements *significant mitigations* to greatly reduce the risk of this denial-of-service vulnerability. These mitigations do not completely eliminate the underlying issue (as that would require changes to GMP itself), but they make successful exploitation *far* more difficult. The mitigations include:
MemoryMonitor class is introduced to track estimated memory usage throughout the library's operations. * This class allows setting a maximum memory limit (defaulting to 1024MB, but configurable). * It provides methods to check_allocation, allocate, and release memory, raising a MemoryError if an operation would exceed the configured limit.check_memory_safety function is used to estimate the memory requirements of various gmpy2 operations *before* they are executed. * This function considers the operation type (exp, mul, pow, mod, polynomial, matrix, polynomial_eval) and the bit lengths of the operands. * It uses conservative estimates and scaling factors to account for gmpy2's internal overhead. * If the estimated memory usage exceeds the limit set by the MemoryMonitor, the operation is rejected *before* calling gmpy2, preventing the crash.CyclicGroup and FeldmanVSS classes now use the check_memory_safety function before performing potentially memory-intensive operations like exp, mul, efficient_multi_exp, _evaluate_polynomial, and _secure_matrix_solve.SecurityError, SerializationError, VerificationError, and ParameterError that include detailed information for forensics and debugging.VSSConfig class allows users to customize the prime_bits and cache_size, enabling them to tailor the library to their specific memory constraints.Limitations of Mitigations:
check_memory_safety function relies on *estimations* of memory usage. While these estimations are conservative, they are not perfect. It is still theoretically possible (though much less likely) for an operation to consume more memory than estimated, leading to a crash.Workarounds (for versions <= 0.7.6b0):
If upgrading to version 0.8.0b2 (or later) is not immediately possible, the following workarounds can help reduce the risk:
check_memory_safety function (available in 0.8.0b2) to manually check the memory usage.Recommendations:
MemoryMonitor in 0.8.0b2 (or later) to set appropriate memory limits for your application. Consider your system's available memory and the expected workload.High Basis: The source's own band: HIGH
0, fixed 0.7.7b0 (ecosystem)0.7.7b0
0.7.7b0pip install --upgrade postquantum-feldman-vss==0.7.7b0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0