[VRP] Ensure untrusted fuzzers do not fuzz in long-lived bots - #5323
Draft
PauloVLB wants to merge 8 commits into
Draft
[VRP] Ensure untrusted fuzzers do not fuzz in long-lived bots#5323PauloVLB wants to merge 8 commits into
PauloVLB wants to merge 8 commits into
Conversation
PauloVLB
force-pushed
the
vrp-untrusted-fuzzer-safety
branch
2 times, most recently
from
June 19, 2026 15:46
85c2781 to
0e2fa1e
Compare
PauloVLB
changed the title
PauloVLB
force-pushed
the
vrp-untrusted-fuzzer-safety
branch
3 times, most recently
from
July 16, 2026 16:04
79ed510 to
c868b40
Compare
PauloVLB
force-pushed
the
vrp-untrusted-fuzzer-safety
branch
3 times, most recently
from
July 16, 2026 20:48
c09e390 to
f3a6d50
Compare
PauloVLB
force-pushed
the
vrp-untrusted-fuzzer-ui
branch
from
July 20, 2026 19:40
1fec842 to
cb4ac9c
Compare
PauloVLB
force-pushed
the
vrp-untrusted-fuzzer-safety
branch
2 times, most recently
from
July 23, 2026 14:11
7e42c64 to
8681bdc
Compare
PauloVLB
force-pushed
the
vrp-untrusted-fuzzer-safety
branch
from
July 29, 2026 13:39
8681bdc to
c094792
Compare
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
Untrusted fuzzers (e.g., external VRP fuzzers) shouldn't run on long-lived bots because they could be malicious or leak sensitive host info. They should only run in isolated, ephemeral environments like Google Cloud Batch.
Proposed Solution
Filter out fuzzers that aren't marked as
trustedfrom being selected by long-lived bots in the task leasing logic.Added runtime assertions (
log_fatal_and_exit) to ensure that if a long-lived bot somehow ends up running an untrusted fuzzer, it will crash immediately before executing any code.Chaining Note
This PR is chained on top of
vrp-untrusted-fuzzer-uiwhich introduces thetrustedfield. Note thattrusteddefaults toTruefor now to maintain compatibility with existing fuzzers without requiring a backfill, but it will be flipped toFalseby default in a future update.Testing
Validated by checking task assignment logic to confirm long-lived bots do not pick up tasks for non-trusted fuzzers. Simulated a forced assignment to verify the fatal crash mechanism works.
Validation
[Insert logs showing long-lived bot rejecting/crashing on non-trusted fuzzer]