Conversation
Summary of ChangesHello @yihaoDeng, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a compilation issue by refining a string copy operation within the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. 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 by creating a comment 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request addresses a potential buffer over-read vulnerability by replacing strlen with sizeof in a strncpy call, which is a good improvement. However, strncpy itself can be unsafe as it does not guarantee null-termination if the source string's length is equal to or greater than the destination buffer size. I've suggested using snprintf as a safer alternative to ensure the string is always null-terminated, preventing potential buffer over-reads in subsequent operations.
|
|
||
| destUser->ver = srcUser->ver; | ||
| strncpy(destUser->user, srcUser->user, strlen(srcUser->user)); | ||
| strncpy(destUser->user, srcUser->user, sizeof(destUser->user)); |
There was a problem hiding this comment.
While using sizeof(destUser->user) is an improvement over strlen(srcUser->user) as it correctly uses the size of the destination buffer, strncpy can still lead to issues. If the source string srcUser->user has a length greater than or equal to sizeof(destUser->user), the destination buffer destUser->user will not be null-terminated. This can lead to buffer over-reads in subsequent operations that treat it as a C-string.
A safer alternative is to use snprintf, which guarantees null-termination.
snprintf(destUser->user, sizeof(destUser->user), "%s", srcUser->user);There was a problem hiding this comment.
Pull request overview
This PR fixes a compile error in the cloneDataTimeWhiteListRsp function by correcting the third parameter of a strncpy call from strlen(srcUser->user) to sizeof(destUser->user).
- Replaces incorrect use of
strlen()withsizeof()for buffer size limit instrncpy
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| destUser->ver = srcUser->ver; | ||
| strncpy(destUser->user, srcUser->user, strlen(srcUser->user)); | ||
| strncpy(destUser->user, srcUser->user, sizeof(destUser->user)); |
There was a problem hiding this comment.
The use of sizeof(destUser->user) is correct but inconsistent with the pattern used elsewhere in this file. Line 5308 uses the constant TSDB_USER_LEN instead: strncpy(pNew->user, src->user, TSDB_USER_LEN);. Consider using TSDB_USER_LEN for consistency, or alternatively ensure null-termination by using sizeof(destUser->user) - 1 followed by explicit null termination.
| strncpy(destUser->user, srcUser->user, sizeof(destUser->user)); | |
| strncpy(destUser->user, srcUser->user, TSDB_USER_LEN); | |
| destUser->user[TSDB_USER_LEN - 1] = '\0'; |
Description
Issue(s)
Checklist
Please check the items in the checklist if applicable.