{"uuid": "4df1eeec-32eb-41d9-acb6-2041e7eaa921", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-24802", "type": "seen", "source": "https://t.me/cvedetector/16815", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-24802 - Plonky2 Lookup Table Padding overwrite vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-24802 \nPublished : Jan. 30, 2025, 8:15 p.m. | 58\u00a0minutes ago \nDescription : 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. \nSeverity: 8.6 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"30 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-30T22:38:10.000000Z"}