chore(dockerfiles/cd): run additional make targets to verify builder#903
chore(dockerfiles/cd): run additional make targets to verify builder#903ti-chi-bot wants to merge 1 commit intomainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Summary of ChangesHello, 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 enhances the Highlights
Changelog
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 adds make targets to the centos7 TiCDC builder Dockerfile to verify the builder's capabilities. However, it introduces a potential command injection vulnerability by using the GOPROXY build argument without proper quoting in a RUN command, which could allow an attacker to execute arbitrary commands. Additionally, a similar change is missing in the rockylinux-based builder Dockerfile (dockerfiles/cd/builders/ticdc/Dockerfile), which should be addressed for consistent verification across all builders.
| ARG GOPROXY | ||
| RUN GOPROXY=${GOPROXY} make cdc -C /ws | ||
| # only for verify the builder. | ||
| RUN GOPROXY=${GOPROXY} make kafka_consumer pulsar_consumer storage_consumer -C /ws |
There was a problem hiding this comment.
The GOPROXY build argument is used in a RUN command without proper quoting, which can lead to a command injection vulnerability if an attacker controls its value. To remediate this, wrap the variable in double quotes. Additionally, for Docker image optimization, consider combining consecutive RUN commands into a single layer, potentially merging this make command with the preceding one to reduce image layers.
RUN GOPROXY="${GOPROXY}" make kafka_consumer pulsar_consumer storage_consumer -C /ws
No description provided.