[ 
https://issues.apache.org/jira/browse/YUNIKORN-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814669#comment-17814669
 ] 

Yu-Lin Chen edited comment on YUNIKORN-2389 at 2/6/24 8:20 AM:
---------------------------------------------------------------

Hi [~chia7712] 
I've checked for CVE in web/release repo using 
[govulncheck|https://go.dev/doc/security/vuln/] and there is no CVE warning 
occurred.

Hi [~wilfreds],
In the similar jira, it appears that updating web/release dependencies for CVE 
is not within the scope.
Could I confirm with you if it required?

- [YUNIKORN-1651] Upgrade golang dependencies for CVEs


was (Author: yu-lin chen):
Hi [~chia7712] 
I've checked for CVE in web/release repo using 
[govulncheck|https://go.dev/doc/security/vuln/] and there is no CVE warning 
occurred.

Hi [~wilfreds],
In the similar jira, it appears that updating web/release dependencies for CVE 
is not within the scope.
Could I confirm with you if it required?
[YUNIKORN-1651] Upgrade golang dependencies for CVEs

> Update golang dependencies
> --------------------------
>
>                 Key: YUNIKORN-2389
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2389
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: release
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Yu-Lin Chen
>            Priority: Critical
>              Labels: pull-request-available
>
> golang.org/x/crypto v0.16.0 is used but it has 
> [CVE-2023-48795|https://www.cve.org/CVERecord?id=CVE-2023-48795] (or 
> GO-2023-2402) and we should upgrade to the latest before the release.
> While we are upgrading that one we should also update the others:
>  * golang.org/x/net v0.20.0
>  * golang.org/x/sys v0.16.0
>  * golang.org/x/text v0.14.0
>  * golang.org/x/tools v0.17.0



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to