Uh oh!
There was an error while loading. Please reload this page.
TEZ-4552. Upgrade protobuf to 3.24.4 due to CVE. - #345
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Aggarwal-Raghav
commented
Apr 13, 2024
@slfan1989, for protobuf version upgrade, you need to update the generated code for the corresponding proto files as well. |
abstractdog
commented
Apr 14, 2024
what kind of generated code upgrade do we expect here? does anything change if we run "mvn clean install -DskipTests"? |
My bad, as per my understanding, for .proto file, the generated code for that corresponding proto file, generally have some changes when we change protobuf version but here its not the case(I should have tested this before commenting 🙁) |
abstractdog
commented
Apr 14, 2024
no worries, thanks for the comments and activity here! |
@slfan1989@abstractdog Can we update protobuf version to 3.24.4? Hive is also using the same version |
slfan1989
commented
Apr 25, 2024
Thanks for your message, I will try to upgrade to 3.24.4. |
BilwaST
commented
May 5, 2024
Thanks for your patch @slfan1989. Looks good to me |
@abstractdog@Aggarwal-Raghav@BilwaST Thank you for paying attention to this pr! The reason I want to upgrade protobuf is because there are some CVE vulnerabilities in lower versions of protobuf, so I try to upgrade protobuf to a higher version to solve related issues. Some known protobuf vulnerabilities: |
This comment was marked as outdated.
This comment was marked as outdated.
tez-yetus
commented
May 5, 2024
💔 -1 overall
This message was automatically generated. |
abstractdog
commented
May 6, 2024
failing unit tests are because of TEZ-4559, this looks good to me |
JIRA: TEZ-4552. Upgrade protobuf to 3.24.4 due to CVE.
I found that there are 3 CVE issues that we need to deal with. These CVE issues are related to protobuf. Our protobuf uses 3.21.1, which is an old version. This PR will try to upgrade the protobuf version to solve the CVE issue.