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:
- Confirmation of a vulnerability including an action
- False Positive
The information related to Repository, Group, Artifact, Version and Problem Code are extracted from the CLM report (see the below screenshot)
There are no known vulnerabilities for our repos:
optf/osdf
optf/has
Repository | Group | Impact Analysis | Action |
---|---|---|---|
optf/cmso | com.fasterxml.jackson.core:jackson-databind:2.9.7 | ||
apache-httpclient:commons-httpclient | Confirmation of vulnerability. | ||
org.codehaus.plexus | Confirmation of vulnerability | ||
commons-collections | Confirmation of vulnerability | ||
xerces:xercesImpl | Confirmation of vulnerability | ||
commons-beanutils:commons-beanutils | Confirmation of vulnerability | ||
dom4j:dom4j:1.6.1 | This dependency is pulled in by hibernate-core. We are using the latest release of Hibernate. CMSO doesn't use dom4j library directly in the code base. | Request Exception. To fix this would require upgrading spring-boot version to 2.1.0-RELEASE |