🛡️ Sentinel: Fix Numerical Instability in Favoritism Module #366
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.
🛡️ Sentinel: [CRITICAL/HIGH] Fix Numerical Instability in Favoritism Module
Vulnerability:
The
calculate_favoritism_scorefunction previously accepted unbounded and invalid floating-point inputs (NaN, Infinity, negative time).NaNinputs intime.twere silently coerced to0.0due tomax(0.0), leading to a score of0.0(Silent Failure).NaNinputs in other fields (e.g., personality) propagatedNaNthrough the system.Fix:
FavoritismInputs::validate().try_calculate_favoritism_scorewhich returnsResult<f64, FavoritismError>.calculate_favoritism_scoreto use the safe version and strictly returnNaNif inputs are invalid, preventing misleading0.0results.find_favorite_childto treat invalid inputs as-Infinity(lowest possible score) rather thanNaN(which breaks sorting/comparison), ensuring robust behavior.Verification:
tests/test_favoritism_security.rsverifying that invalid inputs returnErr(safe version) orNaN(legacy version).tests/test_favoritism.rsstill pass.PR created automatically by Jules for task 7740966389182008347 started by @fderuiter