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

lujie edited comment on YARN-10980 at 10/18/21, 11:20 AM:
----------------------------------------------------------

due to forget to fetech upstream, i open this issue. this bug is fixed by 
https://issues.apache.org/jira/browse/HADOOP-17653.


was (Author: xiaoheipangzi):
it is fixed by https://issues.apache.org/jira/browse/HADOOP-17963

> fix CVE-2020-8908
> -----------------
>
>                 Key: YARN-10980
>                 URL: https://issues.apache.org/jira/browse/YARN-10980
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: lujie
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> see  [https://www.cvedetails.com/cve/CVE-2020-8908/]
>  
> A temp directory creation vulnerability exists in all versions of Guava, 
> allowing an attacker with access to the machine to potentially access data in 
> a temporary directory created by the Guava API 
> com.google.common.io.Files.createTempDir(). By default, on unix-like systems, 
> the created directory is world-readable (readable by an attacker with access 
> to the system). The method in question has been marked @Deprecated in 
> versions 30.0 and later and should not be used. For Android developers, we 
> recommend choosing a temporary directory API provided by Android, such as 
> context.getCacheDir(). For other Java developers, we recommend migrating to 
> the Java 7 API java.nio.file.Files.createTempDirectory() which explicitly 
> configures permissions of 700, or configuring the Java runtime's 
> java.io.tmpdir system property to point to a location whose permissions are 
> appropriately configured.



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