🛡️ Sentinel: [DoS Protection] Add input length limit to version comparison #815
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: [DoS Protection] Add input length limit to version comparison
Vulnerability:
The
compareTofunction split input strings and iterated over them without checking the length. Extremely long version strings (e.g., millions of characters) could be used to cause high CPU/memory usage (DoS).Fix:
MAX_VERSION_LENGTHconstant (256 characters).compareToto returnNaN(which results infalsefor comparisons) if the input length exceeds the limit.Verification:
src/security.test.tsto ensure long strings are rejected and valid long strings (within limit) are accepted.PR created automatically by Jules for task 3146843907473823444 started by @srod
Summary by cubic
Added a 256-character input limit to version comparison to prevent DoS from extremely long version strings. Oversized inputs now fail closed so comparisons return false without heavy processing.
Written for commit 9bec866. Summary will update on new commits.