You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhou Shijie (Jira)" <ji...@apache.org> on 2023/11/02 01:47:00 UTC
[jira] [Comment Edited] (FLINK-33408) Bump the snakeyaml from 1.33 to 2.0 to fix the container vulnerability.
[ https://issues.apache.org/jira/browse/FLINK-33408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781945#comment-17781945 ]
Zhou Shijie edited comment on FLINK-33408 at 11/2/23 1:46 AM:
--------------------------------------------------------------
[~martijnvisser] , I thought these people might be related to my ISSUE, so I mentioned them in the PR, sorry about that. Thanks for your kind reminder (y). I'll avoid it in the future.
was (Author: JIRAUSER302861):
[~martijnvisser] , I thought these people might be related to my ISSUE, so I mentioned them in the PR, sorry about that. Thanks for the warning (y). I'll avoid it in the future.
> Bump the snakeyaml from 1.33 to 2.0 to fix the container vulnerability.
> -----------------------------------------------------------------------
>
> Key: FLINK-33408
> URL: https://issues.apache.org/jira/browse/FLINK-33408
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Affects Versions: 1.18.0
> Reporter: Zhou Shijie
> Priority: Major
> Labels: pull-request-available
>
> Fix the container vulnerability in [CVE-2022-1471|https://github.com/advisories/GHSA-mjmj-j48q-9wg2] by upgrade the SnakeYaml dependency version in flink-kubernetes module.
> Upgrade the Kubernetes Client from 6.6.2 to 6.7.0, thereby upgrading the version of snakeyaml, which the Kubernetes Client indirectly depends on, from 1.33 to 2.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)