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

ASF GitHub Bot commented on HADOOP-17563:
-----------------------------------------

github-actions[bot] commented on PR #3405:
URL: https://github.com/apache/hadoop/pull/3405#issuecomment-3568526985

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> Update Bouncy Castle to 1.68 or later
> -------------------------------------
>
>                 Key: HADOOP-17563
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17563
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.3.1
>            Reporter: Takanobu Asanuma
>            Assignee: PJ Fanning
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0, 3.3.5
>
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> -Bouncy Castle 1.60 has Hash Collision Vulnerability. Let's update to 1.68.-
> Bouncy Castle 1.60 has the following vulnerabilities. Let's update to 1.68.
>  * [https://nvd.nist.gov/vuln/detail/CVE-2020-26939]
>  * [https://nvd.nist.gov/vuln/detail/CVE-2020-28052]
>  * [https://nvd.nist.gov/vuln/detail/CVE-2020-15522]
> for anyone backporting this, note that recent bouncy castle jars are 
> incompatible with older versions of asm.jar, and so older versions of spark.



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