[
https://issues.apache.org/jira/browse/NIFI-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593711#comment-16593711
]
Pierre Villard commented on NIFI-5541:
--------------------------------------
Also, note that a CVE can be detected in a transitive dependency. It would be
up to the direct dependency to change the version of their dependencies,
release a new version, and then we could use the latest version.
Example:
{noformat}
[INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @
nifi-kite-processors ---
[INFO] org.apache.nifi:nifi-kite-processors:jar:1.8.0-SNAPSHOT
[INFO] \- org.apache.hive.hcatalog:hive-hcatalog-core:jar:1.2.1:compile
[INFO] \- org.apache.hive:hive-metastore:jar:1.2.1:compile
[INFO] +- org.apache.thrift:libfb303:jar:0.9.2:compile
[INFO] \- org.apache.thrift:libthrift:jar:0.9.2:compile{noformat}
Even if we upgrade to
{noformat}
hive-hcatalog-core:jar:1.2.2{noformat}
The dependency on libfb303 is the same and we cannot update to 2.x / 3.x
branches as it'd cause breaking changes. We do provide, however, Hive
processors for 3.x for instance.
However, it is easy to remove the bundles concerned by a CVE if you're not
interested in using the processors of that bundle.
It's just an example but the point is: quite often the version update does not
depend on the NiFi community only.
> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
> Key: NIFI-5541
> URL: https://issues.apache.org/jira/browse/NIFI-5541
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Tools and Build
> Affects Versions: 2.0.0, 1.8.0
> Environment: All development, build, test, environments.
> Reporter: Albert Baker
> Assignee: Pierre Villard
> Priority: Major
> Labels: build, easy-fix, 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 that get pulled into the released product via
> dependant/third-party 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 newly discovered &
> reported (known) vulnerailities. Project teams that keep up with removing
> known 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)
