This template is intended to be used to document the outcome of the impact analysis related to the known vulnerability reported by Nexus-IQ (CLM tab in Jenkins).  Nexus-IQ can identify the known vulnerabilities contained in the components use by onap components.

This table will be presented to TSC at Code Freeze milestone (M4) to the TSC.

It is recommended to first update to the latest version of the third party components available. In case the latest third party components still reports some vulnerabilities, you must provide an impact analysis as illustrated in the example below.


The following table is addressing 2 different scenarios:

The information related to Repository, Group, Artifact, Version and Problem Code are extracted from the CLM report (see the below screenshot)


RepositoryGroupImpact AnalysisAction
policy/commoncom.fasterxml.jackson.core

False Positive - we are not using the Jackson code in the manner that exposes the vulnerability.

Request exception

policy/commoncom.fasterxml.jackson.datatypeFalse Positive - we are not using any DurationDeserializer or InstantDeserializer.

Request exception





policy/api

policy/pap

policy/drools-pdp

policy/xacml-pdp

policy/drools-applications

policy/engine

policy/distribution

com.fasterxml.jackson.core

False Positive - flagged due to inheritance of policy/common above.

Request exception

policy/api

policy/pap

policy/drools-pdp

policy/xacml-pdp

policy/drools-applications

policy/engine

policy/distribution


com.fasterxml.jackson.datatype

False Positive - flagged due to inheritance of policy/common above.


Request exception





policy/drools-pdpdom4j

This is both a security and a license issue due to Drools v6.5.0.Final including and using this dependency.

Upgrading to 7.x version would not clear this issue and would result in multiple other license exceptions that are not clearable.

Request exception

policy/drools-pdpjsoup

This is a security issue due to Drools v6.5.0.Final including this dependency.

Upgrading to 7.x version would not clear this issue and would result in multiple other new license exceptions that are not clearable.

Request exception

policy/drools-pdpant

This is a security issue due to Drools v6.5.0.Final including this dependency.

Upgrading to 7.x version would clear this issue, but would then consequently result in multiple other new license exceptions that are not clearable.

Request exception





policy/apex-pdporg.codehaus.jackson.jackson-mapper-asl

This dependency is pulled in by org.apache.avro. We are using the latest version of Avro.

We are using Avro to deserialize events. Avro uses jackson-mapper-asl for its Json decoding. The schema for the events we are decoding is controlled in policy models and prevents executable code being specified. Therefore this vulnerability cannot be exploited.

Request exception

policy/apex-pdporg.python.jython-standalone.2.7.1

This dependency brings in the Jython (Python) interpreter for executing scripts written in Python under the control of Apex.

There are two vulnerabilities, both concerning adding extra modules to the Python libraries on a host running Python scripts under Jython.

  • The setup.py and build_py.py files allow extra python packages to be installed on the host during the startup of Jython. This mechanism uses the setuptools mechanism to install those packages. That mechanism does not enforce path traversal restrictions, allowing malicious packages to access protected areas on the host.
  • Jython uses packages installed with the python pip utility. Pip is vulnerable to Path Traversal attacks, malicious packages installed with pip can access protected areas on the host

The solution is to warn developers not to install malicious extra Python packages.

Request Exception

The apex-pdp documentation for the Jython plugin is updated to warn developers that they must ensure that extra python packages they add at install time with PIP or using the setup.py/build_py.py mechanisms must be checked and certified by them as not being malicious.


policy/apex-pdpdom4j

This dependency is pulled in by hibernate-core. We are using the latest release of Hibernate.

The XML schema of incoming events is controlled in Apex and arbitrary code even if it was injected cannot be executed.

Request exception

policy/apex-pdporg.apache.zookeeper

Liam Fallon - can you take a quick look at the impact?

Request exception








policy/enginecom.fasterxml.jackson.core

False positive

The code is not using jackson in the manner described in the vulnerability.

Request exception

- This is a large amount of work to clear Jackson from this repository. It may not be worth the effort as we will be deprecating the repo in the next 2 or 3 releases.

policy/engineorg.springframeworkOne version is flagged due to inclusion of ONAP Portal SDK

Request exception

policy/engineorg.springframeworkWe will upgrade other versions not related to ONAP Portal SDK. Possible together, needs investigation.

policy/enginebouncycastleFlagged due to inclusion of ONAP Portal SDK

Request exception

policy/enginecom.mchangeFlagged due to inclusion of ONAP Portal SDK

Request exception

policy/engine

angularjs

angular

angular.min.js

angular-ui-grid.js

angular-sanitize

Flagged due to inclusion of ONAP Portal SDK

Request exception

policy/engineng-formio-gridFlagged due to inclusion of ONAP Portal SDK

Request exception

policy/enginewicket-utilFlagged due to inclusion of ONAP Portal SDK

Request exception

policy/engine

moment


moment

Flagged due to inclusion of ONAP Portal SDK

Request exception

policy/enginexercesFlagged due to inclusion of ONAP Portal SDK

Request exception

policy/enginecommons-beanutilsFlagged due to inclusion of ONAP Portal SDK

Request exception

policy/engineesapiFlagged due to inclusion of ONAP Portal SDK

Request exception

policy/engineantisamyFlagged due to inclusion of ONAP Portal SDK

Request exception

policy/enginejqueryFlagged due to inclusion of ONAP Portal SDK

Request exception

policy/enginecommons-fileuploadFlagged due to inclusion of ONAP Portal SDK

Request exception





policy/distributionorg.springframeworkFlagged due to inheritance from policy/engine which has dependency on ONAP Portal SDK

Request exception


Sample of CLM Report