You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Koji Noguchi (Jira)" <ji...@apache.org> on 2020/01/10 22:11:00 UTC

[jira] [Resolved] (PIG-5352) Please add OWASP Dependency Check to the build (ivy.xml)

     [ https://issues.apache.org/jira/browse/PIG-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koji Noguchi resolved PIG-5352.
-------------------------------
    Hadoop Flags: Reviewed
    Release Note: 
Now 
% ant owasp
would create a report for known vulnerabilities for the jars Pig depend on at ./build/owasp. 
      Resolution: Fixed

Thanks for the review Rohini!    Committed to trunk (0.18). 

Also, thanks Albert for creating this jira and sorry it took this long for setting up the report.
For the actual vulnerabilities reported with this tool, we will create new jiras for tracking them.
 

> Please add OWASP Dependency Check to the build (ivy.xml)
> --------------------------------------------------------
>
>                 Key: PIG-5352
>                 URL: https://issues.apache.org/jira/browse/PIG-5352
>             Project: Pig
>          Issue Type: New Feature
>          Components: build
>    Affects Versions: 0.15.1, 0.17.0, 0.16.1, 0.18.0, 0.17.1
>         Environment: All development, build, test, environments.
>            Reporter: Albert Baker
>            Assignee: Koji Noguchi
>            Priority: Major
>              Labels: security
>             Fix For: 0.18.0
>
>         Attachments: pig-5352-v01.patch
>
>
> Please add OWASP Dependency Check to the build (pom.xml). OWASP DC makes an outbound REST call to MITRE Common Vulnerabilities & Exposures (CVE) to perform a lookup for each dependant .jar to list any/all known vulnerabilities for each jar. This step is needed because a manual MITRE CVE lookup/check on the main component does not include checking for vulnerabilities in components or in dependant libraries.
> OWASP Dependency check : https://www.owasp.org/index.php/OWASP_Dependency_Check has plug-ins for most Java build/make types (ant, maven, ivy, gradle).
> Also, add the appropriate command to the nightly build to generate a report of all known vulnerabilities in any/all third party libraries/dependencies that get pulled in. example : mvn -Powasp -Dtest=false -DfailIfNoTests=false clean aggregate
> Generating this report nightly/weekly will help inform the project's development team if any dependant libraries have a reported known vulnerailities. Project teams that keep up with removing vulnerabilities on a weekly basis will help protect businesses that rely on these open source componets.



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