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

Koji Noguchi reassigned PIG-5352:
---------------------------------

    Fix Version/s: 0.18.0
       Patch Info: Patch Available
         Assignee: Koji Noguchi
           Labels: security  (was: build easyfix security)

We should have done this a long time back but better late than never.
With the patch, 
{{% ant owasp}} 
would create a report at 
{noformat}
knoguchi pig> ls build/owasp/
dependency-check-junit.xml    dependency-check-report.html  
dependency-check-report.xml
dependency-check-report.csv   dependency-check-report.json
knoguchi pig>
{noformat}

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

Reply via email to