Potential fix for code scanning alert no. 149: Possibly wrong buffer size in string copy #14
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.
Potential fix for https://github.com/IntelLabs/async-toolkit/security/code-scanning/149
The safest, clearest fix is to replace the calls to
strncpy(..., strlen(...)+1)on lines 123, 126, and 129 withstrcpy(...). This reflects the dynamic allocation that matches the source length, always including the null terminator. We should make this change for all three similar cases for consistency and clarity. No import or further definition changes are required, asstrcpyis already available via<string.h>. Only these lines in the code block need modification.Suggested fixes powered by Copilot Autofix. Review carefully before merging.