directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn McKinney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FC-240) Please add OWASP Dependency Check to the build (pom.xml)
Date Fri, 07 Sep 2018 15:12:00 GMT

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

Shawn McKinney commented on FC-240:
-----------------------------------

Another problem running the owasp plug-in, requires maven 3.1.  Once I installed that, and
filtered out openldap serverside CVE's, the tests passed:

 

[INFO] --- dependency-check-maven:3.3.1:check (default) @ fortress-core ---
[INFO] Central analyzer disabled
[INFO] Checking for updates
[INFO] Skipping NVD check since last check was within 4 hours.
[INFO] Skipping RetireJS update since last update was within 24 hours.
[INFO] Check for updates complete (13 ms)
[INFO] Analysis Started
[INFO] Finished Archive Analyzer (0 seconds)
[INFO] Finished File Name Analyzer (0 seconds)
[INFO] Finished Jar Analyzer (0 seconds)
[INFO] Finished Dependency Merging Analyzer (0 seconds)
[INFO] Finished Version Filter Analyzer (0 seconds)
[INFO] Finished Hint Analyzer (0 seconds)
[INFO] Created CPE Index (1 seconds)
[INFO] Skipping CPE Analysis for npm
[INFO] Finished CPE Analyzer (1 seconds)
[INFO] Finished False Positive Analyzer (0 seconds)
[INFO] Finished NVD CVE Analyzer (0 seconds)
[INFO] Finished Vulnerability Suppression Analyzer (0 seconds)
[INFO] Finished Dependency Bundling Analyzer (0 seconds)
[INFO] Analysis Complete (2 seconds)
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ fortress-core ---
[INFO] Installing /home/smckinn/GIT/fortressDev/directory-fortress-core/target/fortress-core-2.0.2-SNAPSHOT.jar
to /home/smckinn/.m2/repository/org/apache/directory/fortress/fortress-core/2.0.2-SNAPSHOT/fortress-core-2.0.2-SNAPSHOT.jar
[INFO] Installing /home/smckinn/GIT/fortressDev/directory-fortress-core/pom.xml to /home/smckinn/.m2/repository/org/apache/directory/fortress/fortress-core/2.0.2-SNAPSHOT/fortress-core-2.0.2-SNAPSHOT.pom
[INFO] Installing /home/smckinn/GIT/fortressDev/directory-fortress-core/target/fortress-core-2.0.2-SNAPSHOT-tests.jar
to /home/smckinn/.m2/repository/org/apache/directory/fortress/fortress-core/2.0.2-SNAPSHOT/fortress-core-2.0.2-SNAPSHOT-tests.jar
[INFO] Installing /home/smckinn/GIT/fortressDev/directory-fortress-core/target/fortress-core-2.0.2-SNAPSHOT-sources.jar
to /home/smckinn/.m2/repository/org/apache/directory/fortress/fortress-core/2.0.2-SNAPSHOT/fortress-core-2.0.2-SNAPSHOT-sources.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS

> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
>                 Key: FC-240
>                 URL: https://issues.apache.org/jira/browse/FC-240
>             Project: FORTRESS
>          Issue Type: New Feature
>    Affects Versions: 2.0.2, 3.0.1-RC1
>         Environment: All development, build, test, environments.
>            Reporter: Albert Baker
>            Assignee: Shawn McKinney
>            Priority: Major
>              Labels: build, easy-fix, security
>             Fix For: 2.0.2
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
>  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
(v7.6.3#76005)

Mime
View raw message