fix: check return value of output_policy.is_valid() in is_execution_allowed #9396
+3
−1
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.
Summary
Fixes #9391
UserCodeService.is_execution_allowed()callsoutput_policy.is_valid(context)but discards its boolean return value. Only exceptions fromis_valid()were caught, so whenis_valid()returnedFalsewithout raising an exception, execution was incorrectly allowed.Root Cause
This means policies like
SingleExecutionExactOutput-- which returnFalseon subsequent calls rather than raising -- were silently bypassed, allowing multiple executions when only one should be permitted.Fix
Now:
is_valid()returnsFalse->INVALID_OUTPUT_POLICYis_valid()raises an exception ->INVALID_OUTPUT_POLICYis_valid()returnsTrue->ALLOWEDImpact
This is a security-relevant fix. Without it, output policies that signal invalidity via return value (rather than exception) are ineffective, allowing unauthorized repeated execution of user code.
Test Plan
SingleExecutionExactOutputpolicy correctly blocks a second execution attemptTrueon valid state continue to allow execution