CVE-2025-52484

{"id": "CVE-2025-52484", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 2.7, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "LOW", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "UNREPORTED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "LOW", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-06-20T18:15:28.747", "references": [{"url": "https://github.com/risc0/risc0/commit/006d86c363b16d2b2ac42d32d832a209ff8ab4c9", "source": "security-advisories@github.com"}, {"url": "https://github.com/risc0/risc0/commit/1873bbb8a56793edd1f6195242d184cf6cc5175d", "source": "security-advisories@github.com"}, {"url": "https://github.com/risc0/risc0/commit/67f2d81c638bff5f4fcfe11a084ebb34799b7a89", "source": "security-advisories@github.com"}, {"url": "https://github.com/risc0/risc0/pull/3181", "source": "security-advisories@github.com"}, {"url": "https://github.com/risc0/risc0/security/advisories/GHSA-g3qg-6746-3mg9", "source": "security-advisories@github.com"}, {"url": "https://github.com/risc0/zirgen/commit/e0e2918302c93e956f73ca2e44aef2b861d8c3ae", "source": "security-advisories@github.com"}, {"url": "https://github.com/risc0/zirgen/pull/238", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-345"}]}], "descriptions": [{"lang": "en", "value": "RISC Zero is a general computing platform based on zk-STARKs and the RISC-V microarchitecture. Due to a missing constraint in the rv32im circuit, any 3-register RISC-V instruction (including remu and divu) in risc0-zkvm 2.0.0, 2.0.1, and 2.0.2 are vulnerable to an attack by a malicious prover. The main idea for the attack is to confuse the RISC-V virtual machine into treating the value of the rs1 register as the same as the rs2 register due to a lack of constraints in the rv32im circuit. Rust applications using the risc0-zkvm crate at versions 2.0.0, 2.0.1, and 2.0.2 should upgrade to version 2.1.0. Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.1 is active on all official routers, and version 2.0 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.1 version of the verifier."}, {"lang": "es", "value": "RISC Zero es una plataforma inform\u00e1tica general basada en zk-STARKs y la microarquitectura RISC-V. Debido a la ausencia de una restricci\u00f3n en el circuito rv32im, cualquier instrucci\u00f3n RISC-V de 3 registros (incluyendo remu y divu) en risc0-zkvm 2.0.0, 2.0.1 y 2.0.2 es vulnerable a un ataque de un probador malicioso. El objetivo principal del ataque es confundir a la m\u00e1quina virtual RISC-V para que trate el valor del registro rs1 como el del registro rs2 debido a la ausencia de restricciones en el circuito rv32im. Las aplicaciones Rust que utilizan el crate risc0-zkvm en las versiones 2.0.0, 2.0.1 y 2.0.2 deben actualizarse a la versi\u00f3n 2.1.0. Las aplicaciones de contratos inteligentes que utilizan el enrutador verificador RISC Zero no necesitan realizar ninguna acci\u00f3n: la versi\u00f3n 2.1 de zkVM est\u00e1 activa en todos los enrutadores oficiales y la versi\u00f3n 2.0 se ha deshabilitado. Las aplicaciones de contratos inteligentes que no utilizan el enrutador verificador deben actualizar sus contratos para enviar llamadas de verificaci\u00f3n a la versi\u00f3n 2.1 del verificador."}], "lastModified": "2025-06-23T20:16:21.633", "sourceIdentifier": "security-advisories@github.com"}