Bind rmqID instead of using stringWithFormat. #14856
Merged
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.
When populating SQL queries to find messages by ID,
stringWithFormat
is currently being used.firebase-ios-sdk/FirebaseMessaging/Sources/FIRMessagingRmqManager.m
Lines 280 to 287 in 1deb75c
This is a potential SQL injection vulnerability. Even though it's very unlikely to be exploited since the
rmqID
is not user input, but a Google generated ID, we should follow best practices and usesqlite3_bind_text
to bind the value instead.This PR introduces no behavioral changes. It just changes how the SQL query is populated.
#14846.