[
https://issues.apache.org/jira/browse/HADOOP-19289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921348#comment-17921348
]
ASF GitHub Bot commented on HADOOP-19289:
-----------------------------------------
pjfanning commented on PR #7072:
URL: https://github.com/apache/hadoop/pull/7072#issuecomment-2615541597
I've seen those decommission tests fail in a few builds recently - in
different PRs so not seemingly caused by the PR changes.
Protobuf-Java 3.25.6 has just come out but has a major breaking change where
it fails at runtime if you have Protobuf Generated Java code that is too old
(ie generated with a fairly old version of protoc). Unfortunately, this doesn't
seem uncommon. HBase looks like it will be quite affected. I came across the
issue in Apache Pekko.
https://github.com/apache/pekko/pull/1748
> upgrade to protobuf-java 3.25.5 due to CVE-2024-7254
> ----------------------------------------------------
>
> Key: HADOOP-19289
> URL: https://issues.apache.org/jira/browse/HADOOP-19289
> Project: Hadoop Common
> Issue Type: Task
> Components: common
> Reporter: PJ Fanning
> Assignee: PJ Fanning
> Priority: Major
> Labels: pull-request-available
> Fix For: thirdparty-1.4.0, thirdparty-1.3.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> https://github.com/advisories/GHSA-735f-pc8j-v9w8
> Presumably protobuf encoded messages in Hadoop come from trusted sources but
> it is still useful to upgrade the jar.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
