0xPolygonZero plonky2 1.0.0 cryptographic primitive risky implementation

Summaryinfo

A vulnerability identified as problematic has been detected in 0xPolygonZero plonky2 1.0.0. This impacts an unknown function. The manipulation leads to cryptographic primitive risky implementation. This vulnerability is traded as CVE-2025-24802. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in 0xPolygonZero plonky2 1.0.0. This issue affects some unknown functionality. The manipulation with an unknown input leads to a cryptographic primitive risky implementation vulnerability. Using CWE to declare the problem leads to CWE-1240. To fulfill the need for a cryptographic primitive, the product implements a cryptographic algorithm using a non-standard, unproven, or disallowed/non-compliant cryptographic implementation. Impacted is integrity. The summary by CVE is:

Plonky2 is a SNARK implementation based on techniques from PLONK and FRI. Lookup tables, whose length is not divisible by 26 = floor(num_routed_wires / 3) always include the 0 -> 0 input-output pair. Thus a malicious prover can always prove that f(0) = 0 for any lookup table f (unless its length happens to be divisible by 26). The cause of problem is that the LookupTableGate-s are padded with zeros. A workaround from the user side is to extend the table (by repeating some entries) so that its length becomes divisible by 26. This vulnerability is fixed in 1.0.1.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-24802 since 01/23/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.0.1 eliminates this vulnerability. Applying the patch 091047f7f10cae082716f3738ad59a583835f7b6 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• 0xPolygonZero

Name

• plonky2

Version

• 1.0.0

License

• open-source

Website

• Product: https://github.com/0xPolygonZero/plonky2/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion