Protect against buffer overflows and null pointer dereferences #9
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.


This changeset should resolve all Security and Reliability bugs detected by SonarQube
Potential buffer overflow in bstrlib.c:
bformata() and bassignformat() have calls to vsnprintf() that can potentially overflow the buffer if the value of the second parameter (length) is extremely large
This adds some validation that bails out if the value reaches INT_MAX
Potential null pointer dereference in bstest.c:
The check framework does an assertion for null pointers in the test data, but continues test execution even when the assertion fails, which leads to the potential null pointer dereference when subsequent tests does other assertions on the same pointers
Now we instead abort the test with ck_abort_msg() when a null pointer is encountered