PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Unverified evaluations in Dusk’s PLONK

osec.io | blog | #web3 | #vulnerability-research | #vulnerability | #blockchain | #zero-knowledge | #plonk | #dusk | #soundness
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

OtterSec finds a critical soundness flaw in dusk-plonk: the verifier never validated four prover-supplied polynomial commitments, enabling forged proofs and minting DUSK from nothing.
Published
Collected

Related coverage

blog · osec.io
Unfaithful claims: breaking 6 zkVMs
OtterSec breaks soundness in six zkVMs — Jolt, Nexus, Cairo-M, Ceno, Expander, Binius64 — where unbound prover values let attackers prove false statements after seeing Fiat-Shamir challenges.
blog · certik.com
CertiK Formally Verifies zkWasm, Proving Mathematical Soundness of a Leading zkVM
CertiK’s formal verification of zkWasm provides mathematical proof that a leading zero-knowledge virtual machine executes programs correctly — a rigor level beyond traditional audits, now validated for ACM CCS 2026.
blog · certik.com
What Is a Zero-Knowledge Virtual Machine (zkVM)?
A zkVM combines zero-knowledge proofs with virtual machines to prove a program ran correctly without re-execution or exposing internal data, enabling scalable, privacy-preserving computation.
research · github.com
Steal My Bitcoin Challenge Writeup: PHP 8.4.26 Session Upload Progress Memory Exhaustion Analysis
Provides a detailed binary-level case study on PHP Zend memory manager behavior and worker state persistence after fatal out-of-memory errors.
blog · osec.io
PoRv2: a fast, transparent ZK-based proof of reserves
OtterSec and Backpack open-source PoRv2, a fast ZK proof-of-reserves system with recursive plonky2 circuits and a verifier server, letting users verify exchange solvency without trusting auditors.
blog · osec.io
Move: an auditor’s introduction
OtterSec's auditor-focused introduction to Move: how its type system and resource model enable safer programming, anti-patterns to avoid, and design tips for safer protocols.
Back