[
https://issues.apache.org/jira/browse/FC-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607231#comment-16607231
]
Shawn McKinney commented on FC-240:
-----------------------------------
For some odd reason, the scanner tags openldap accelerator jars,(api & impl) to
openldap server-side vulnerabilities. I am guessing this is because of the
naming convention on the jars. Of course server-side problems shouldn't be
tied to client-side jars.
Suppress all warnings about openldap server:
<?xml version="1.0" encoding="UTF-8"?>
<suppressions
xmlns="https://jeremylong.github.io/DependencyCheck/dependency-suppression.1.1.xsd";>
<!-- Suppress OWASP warnings about openldap serverside vulnerabilities, not
applicable here. -->
<suppress>
<notes><![CDATA[
file name: accelerator-api-1.0-RC41.jar
]]></notes>
<gav regex="true">^org\.openldap:accelerator-api:.*$</gav>
<cpe>cpe:/a:openldap:openldap</cpe>
</suppress>
<suppress>
<notes><![CDATA[
file name: accelerator-impl-1.0-RC41.jar
]]></notes>
<gav regex="true">^org\.openldap:accelerator-impl:.*$</gav>
<cpe>cpe:/a:openldap:openldap</cpe>
</suppress>
</suppressions>
> 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)
