Potential fix for code scanning alert no. 2: Use of string after lifetime ends #45
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/flatcar/update_engine/security/code-scanning/2
To fix the issue, we need to ensure that the lifetime of the
std::string
object returned byGet(index)
is extended so that the pointer returned byc_str()
remains valid. The best way to achieve this is to store thestd::string
object in a local variable within theGetCStr
method and return the pointer to its character array. This ensures that thestd::string
object outlives the call toc_str()
.Changes will be made to the
GetCStr
method in theUrlTerms
class. Specifically:Get(index)
in a local variable.c_str()
on the local variable and return the pointer.No additional imports or dependencies are required for this fix.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.