[
https://issues.apache.org/jira/browse/AVRO-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120149#comment-17120149
]
Zezeng Wang commented on AVRO-2204:
-----------------------------------
In an increasingly complex network environment, network security is
particularly important. From this point, I agree that it is necessary to add
such inspection tools.
But there are some situations that I think need to be discussed:
1. First of all, it is certain that owasp cannot be used as an avro
distribution package.
2. Avro is often used as a dependent library by other projects. If it is
appropriate to go to Avro to check
3. For the first time, owasp will update the local cache of NVD data from NIST.
This process takes 10 minutes or more (I tested this time locally, but
unfortunately
[owasp#2262|https://github.com/jeremylong/DependencyCheck/issues/2262] The
problem of H2 database corruption, this problem is still not resolved), this
may exceed the CI build time and is not recommended as part of the build.
4. There are 4 ways of owasp, command line, ant task, maven plugin, jenkins
plugin, using maven plugin is not necessarily a preference, and I think it will
be more suitable to use as a jenkins plugin.
Do you have any opinion on this?
> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
> Key: AVRO-2204
> URL: https://issues.apache.org/jira/browse/AVRO-2204
> Project: Apache Avro
> Issue Type: New Feature
> Components: java
> Affects Versions: 1.9.0, 1.8.2, 1.10.0
> Environment: All development, build, test, environments.
> Reporter: Albert Baker
> Priority: Major
> Labels: build, easyfix, security
> 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
(v8.3.4#803005)
