[GitHub] [aurora] larrycameron80 opened a new issue #85: Unsafe Dependancy Resolution

[GitBox <gi...@apache.org>]

larrycameron80 opened a new issue #85: Unsafe Dependancy Resolution
URL: https://github.com/apache/aurora/issues/85
 
 
   Unsafe Dependancy Resolution
   Vulnerable module: com.beust:jcommander
   Introduced through: com.beust:jcommander@1.72 and org.asynchttpclient:async-http-client@2.0.37
   Detailed paths
   Introduced through: apache/aurora@apache/aurora#ea8e2f4d905e26b3b999e8b59a3cb74a08a3dbf5 › com.beust:jcommander@1.72
   Remediation: Upgrade to com.beust:jcommander@1.75.
   Introduced through: apache/aurora@apache/aurora#ea8e2f4d905e26b3b999e8b59a3cb74a08a3dbf5 › org.asynchttpclient:async-http-client@2.0.37 › com.typesafe.netty:netty-reactive-streams@1.0.8 › org.testng:testng@6.9.4 › com.beust:jcommander@1.72
   Introduced through: apache/aurora@apache/aurora#ea8e2f4d905e26b3b999e8b59a3cb74a08a3dbf5 › org.asynchttpclient:async-http-client@2.0.37 › com.typesafe.netty:netty-reactive-streams@1.0.8 › org.reactivestreams:reactive-streams-tck@1.0.0 › org.testng:testng@6.9.4 › com.beust:jcommander@1.72
   Overview
   com.beust:jcommander is a Command line parsing framework for Java.
   
   Affected versions of this package are vulnerable to Unsafe Dependancy Resolution due to resolving dependencies over an insecure channel (http).
   
   If the build occurred over an insecure connection, a malicious user could have perform a Man-in-the-Middle attack during the build and alter the build artifacts that were produced. In case that any of these artifacts were compromised, any developers using these could be altered.
   
   Note: In order to validate that this artifact was not compromised, the maintainer would need to confirm that none of the artifacts published to the registry were not altered with. Until this happens, we can not guarantee that this artifact was not compromised even though the probability that this happened is low.
   
   We have chosen to alert on this issue when maintainers either decided to issue CVEs themselves, or in cases when maintainers decided against performing audits on there build to verify they had not been compromised.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services