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

Sean Mackrory commented on HADOOP-15504:
----------------------------------------

[~ajisakaa] I'm only referring to the version of things like maven-core, etc. 
we depend on, not the maven version used to run the build. To get past the 
security issues involved, we need to update to 3.0.5 or higher. I would assume 
that unless there's a bug, that if we don't go above 3.3, it has no impact on 
what versions you can use to run the build.

> Upgrade Maven and Maven Wagon versions
> --------------------------------------
>
>                 Key: HADOOP-15504
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15504
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Major
>
> I'm not even sure that Hadoop's combination of the relevant dependencies is 
> vulnerable (even if they are, this is a relatively minor vulnerability), but 
> this is at least showing up as an issue in automated vulnerability scans. 
> Details can be found here [https://maven.apache.org/security.html] 
> (CVE-2013-0253, CVE-2012-6153). Essentially the combination of maven 3.0.4 
> (we use 3.0, and I guess that maps to 3.0.4?) and older versions of wagon 
> plugin don't use SSL properly (note that we neither use the WebDAV provider 
> nor a 2.x version of the SSH plugin, which is why I suspect that the 
> vulnerability does not affect Hadoop).
> I know some dependencies can be especially troublesome to upgrade - I suspect 
> that Maven's critical role in our build might make this risky - so if anyone 
> has ideas for how to more completely test this than a full build, please 
> chime in,



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to