[ 
https://issues.apache.org/jira/browse/HADOOP-18311?focusedWorklogId=792006&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-792006
 ]

ASF GitHub Bot logged work on HADOOP-18311:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Jul/22 11:01
            Start Date: 18/Jul/22 11:01
    Worklog Time Spent: 10m 
      Work Description: steveloughran commented on PR #4491:
URL: https://github.com/apache/hadoop/pull/4491#issuecomment-1187077914

   this patch includes another aws sdk update in a9c174b7d3e69b6eee1e271.
   
   steve, this merits a whole new jira with full qualification. as now it is 
very, very late to get it into 3.3.4, though I know we will get complaints if 
it isn't




Issue Time Tracking
-------------------

    Worklog Id:     (was: 792006)
    Time Spent: 3h 10m  (was: 3h)

> Upgrade dependencies to address several CVEs
> --------------------------------------------
>
>                 Key: HADOOP-18311
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18311
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: common
>    Affects Versions: 3.3.3, 3.3.4
>            Reporter: Steve Vaughan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.3.4
>
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> The following CVEs can be addressed by upgrading dependencies within the 
> build.  This includes a replacement of HTrace with a noop implementation.
>  * CVE-2018-7489
>  * CVE-2020-10663
>  * CVE-2020-28491
>  * CVE-2020-35490
>  * CVE-2020-35491
>  * CVE-2020-36518
>  * PRISMA-2021-0182
> This addresses all of the CVEs from 3.3.3 except for ones that would require 
> upgrading Netty to 4.x.  I'll be submitting a pull request for 3.3.4.



--
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