Approved changes feed: RSS · Atom
cpe:2.3:a:0xpolygonzero:plonky2:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | 0Xpolygonzero (c021cc98-995c-539b-b316-d8f93ad64a3f) |
|---|---|
| Product | Plonky2 (a321c9d9-7581-5ef7-ba6c-024e461b7291) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-24802 |
vulnerable | 2026-06-08 07:12:49.908623 |
Soundness issue with Plonky2 look up tables
HIGH (8.6)
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.
Published: 2025-01-30T19:20:14.250Z
Updated: 2025-01-30T19:55:17.620Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.