-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Bind rmqID instead of using stringWithFormat. #14856
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This is to fix #14846.
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Could you also please add a changelog entry that references the original issue? |
Also update changelog.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
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.