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

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

                Author: ASF GitHub Bot
            Created on: 12/May/21 01:57
            Start Date: 12/May/21 01:57
    Worklog Time Spent: 10m 
      Work Description: aajisaka merged pull request #2974:
URL: https://github.com/apache/hadoop/pull/2974


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


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

            Worklog Id:     (was: 594993)
    Remaining Estimate: 0h
            Time Spent: 10m

> Update commons-io to 2.8.0
> --------------------------
>
>                 Key: HADOOP-17683
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17683
>             Project: Hadoop Common
>          Issue Type: Task
>            Reporter: Wei-Chiu Chuang
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://nvd.nist.gov/vuln/detail/CVE-2021-29425
> In Apache Commons IO before 2.7, When invoking the method 
> FileNameUtils.normalize with an improper input string, like "//../foo", or 
> "\\..\foo", the result would be the same value, thus possibly providing 
> access to files in the parent directory, but not further above (thus 
> "limited" path traversal), if the calling code would use the result to 
> construct a path value.
> We don't use this API in the Hadoop code, but it's still good to update 
> anyway (we're on 2.5, which is 4 years old)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to