[VRP] Mark testcases as untrusted if generated by untrusted fuzzers - #5330
Open
PauloVLB wants to merge 1 commit into
Open
[VRP] Mark testcases as untrusted if generated by untrusted fuzzers#5330PauloVLB wants to merge 1 commit into
PauloVLB wants to merge 1 commit into
Conversation
PauloVLB
changed the title
PauloVLB
force-pushed
the
vrp-untrusted-testcases-from-fuzzers
branch
4 times, most recently
from
July 16, 2026 20:34
980a389 to
e46384a
Compare
PauloVLB
force-pushed
the
vrp-untrusted-testcases-from-fuzzers
branch
from
July 16, 2026 20:54
e46384a to
29cebfd
Compare
PauloVLB
force-pushed
the
vrp-untrusted-testcases-from-fuzzers
branch
from
August 10, 2026 13:57
29cebfd to
d37c251
Compare
PauloVLB
marked this pull request as ready for review
August 10, 2026 14:01
dylanjew
approved these changes
Aug 10, 2026
PauloVLB
force-pushed
the
vrp-untrusted-testcases-from-fuzzers
branch
from
August 10, 2026 16:19
d37c251 to
77191fb
Compare
PauloVLB
force-pushed
the
vrp-untrusted-testcases-from-fuzzers
branch
from
August 11, 2026 14:24
77191fb to
afb4d58
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
2 participants
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
Testcases generated by untrusted fuzzers should also be treated as untrusted. Currently, they inherit default trust settings, which could lead to them being executed in insecure environments or synced incorrectly.
Proposed Solution
Propagate the trust status from the
Fuzzerto the generatedTestcase.In
fuzz_task.py, we now check thetrustedfield of the generating fuzzer. If the fuzzer is untrusted (trusted=False), the resulting testcase is also marked astrusted=False.Chaining Note
Chained on top of
vrp-untrusted-fuzzer-safety(which usestrustedfield instead ofuntrusted).Testing
Added unit tests in
fuzz_task_test.pyto verify both trusted and untrusted fuzzer scenarios.Validation
Due to the difficulty of testing this in the dev environment (which would require a fuzzer to generate a testcase) and the lack of real untrusted fuzzers in production, this will be tested in the production environment.