[VRP] Untrusted fuzzer UI#5329
Open
PauloVLB wants to merge 1 commit into
Open
Conversation
PauloVLB
force-pushed
the
vrp-untrusted-fuzzer-ui
branch
from
June 17, 2026 16:05
37f5d31 to
8d2a70a
Compare
PauloVLB
force-pushed
the
vrp-untrusted-fuzzer-ui
branch
2 times, most recently
from
July 15, 2026 19:42
6deb047 to
7feb0e9
Compare
PauloVLB
force-pushed
the
vrp-untrusted-fuzzer-ui
branch
from
July 16, 2026 16:04
7feb0e9 to
ec90403
Compare
PauloVLB
marked this pull request as ready for review
July 16, 2026 23:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
We need a way to identify fuzzers that are "untrusted" (e.g., external fuzzers provided by VRP researchers) so we can apply different security policies to them (like restricting where they can run). Currently, there is no field in the UI or Datastore to mark a fuzzer as untrusted.
Proposed Solution
Add an
untrustedboolean field to theFuzzermodel in Datastore and expose it as a simple checkbox in the Fuzzer management UI. This allows admins to easily mark specific fuzzers as untrusted.UI Change
Trying to upload a untrusted fuzzer for a non-linux job gives an error:
Testing
Validated by deploying to dev and verifying that the checkbox state is correctly persisted to and loaded from Datastore.
Validation
I have uploaded a fuzzer with
untrustedset to true; here is a screenshot.