Fix code scanning alert no. 50: Size computation for allocation may overflow #1088
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.
Fixes https://github.com/wavetermdev/waveterm/security/code-scanning/50
To fix the problem, we need to ensure that the size computation for the allocation does not overflow. This can be achieved by validating the length of
barr
before performing the arithmetic operation. We will set a maximum allowable size forbarr
to ensure that the sum ofoscPrefixLen(oscNum)
andlen(barr)
does not exceed the maximum value for anint
.barr
(e.g., 64 MB).barr
against this maximum size before performing the allocation.barr
exceeds the maximum size, return an error.Suggested fixes powered by Copilot Autofix. Review carefully before merging.