Skip to content

Add zkVM bugs #57

Description

@StefanosChaliasos

UI changes:

  • Add ZKVM field to both reports and bugs. It should be a boolean flag.
  • Update the UI to filter bugs and reports with the ZKVM flag.
  • Update the past reports to include the flag and to contain the zkbugs_get_sources.sh file. This file should do nothing if the code is already in the bug report.
  • Add script to run all the zkbugs_get_sources.sh commands in all issues.

For audit reports, also add them in the reports/ directory.
We only include medium, high, and critical severity bugs from audits.
For each bug, we need to do the following:

  1. Create a directory dataset/dsl/project/bug-id where dsl is the DSL used by the project (e.g., plonky3), project is the project name (e.g., SP1), bug-id is the ID that should be source-bug, where source could be the security company (e.g., zksecurity) or a competition or the handle of a security researcher, and bug is the bug name with underscores instead of spaces.
  2. Copy the contents of the template into the new directory: cp template/* dataset/dsl/project/bug-id
  3. Fill all the details in the zkbugs_config.json file. Note that id is source-report-id where report-i is the id for the bug in the report (e.g., 1)
  4. If it is possible to reproduce the bug with a test case, then fill the rest of the files (look at circom-template for an example). In any case, in zkbugs_get_sources.sh add the code to clone the code in the specific commit where the code was vulnerable.

SP1:

risc0:

Zisk:

openvm:

zksync-airbender:

jolt:

Pico and Ziren: Nothing yet

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions