Fix runtime validation bypass by removing asserts in metrics#13
Open
Fix runtime validation bypass by removing asserts in metrics#13
Conversation
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.
Summary
This PR fixes 1 security vulnerability identified by BoostSecurity.
Replace runtime asserts with explicit exceptions in metrics in
twml/twml/contrib/metrics/metrics.py(Line: 58)Risk:
assertstatements were used for runtime input validation inmetrics.py. Python can strip asserts under-O/-OO, allowing invalid indices/parameters to bypass checks and potentially break metric computation in production.Fix: Replaced the asserts with explicit
ValueError/TypeErrorexceptions so validation is always enforced regardless of optimization flags.Review notes: Behavior changes from
AssertionErrortoValueError/TypeErrorfor invalid inputs.Generated by BoostSecurity Advisor