[cfg] Add 'bugprone-suspicious-memory-comparison' to config #3410
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.
The checker landed recently in
3373e845398bfb8fa0e3c81b7ca84cbfedbad3ae
1,and covers SEI-CERT rules EXP42-C 2 and FLP37-C 3 in the same
implementation.
SEI-CERT classifies EXP42-C as Medium severity with Probable likelihood,
while FLP37-C is of Low severity and Unlikely likelihood.
Due to the fix of the issue being minimal engineering effort (making a
comparison predicate and replacing uses of
(std::)memcmp
with it), theMEDIUM
severity in our case I believe is justified.CC: @steakhal