Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

table represents the known exploitable and non-exploitable vulnerabilities in third party packages used in the project.


There are no known vulnerabilities in the optf/osdf and optf/has reposoptf/has

RepositoryGroupImpact AnalysisAction
optf/cmsocom.fasterxml.jackson.core:jackson-databind:2.9.7Confirmation of vulnerability.

Ensure that messages being de-serialized by Spring Boot are from trusted sources

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-397
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-390


apache-httpclient:commons-httpclient

Confirmation of vulnerability.


merged into next buildFixed & removed the jars

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-395


org.codehaus.plexusConfirmation of vulnerability

merged into next buildFixed & removed the jars

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-395


commons-collectionsConfirmation of vulnerability

merged into next buildFixed & removed the jars

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-395


xerces:xercesImplConfirmation of vulnerability

merged into next buildFixed & removed the jars

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-395


commons-beanutils:commons-beanutilsConfirmation of vulnerability

merged into next buildFixed & removed the jars

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-395


 dom4j:dom4j:1.6.1

This dependency is pulled in by hibernate-core. dom4j is used internally in the hibernate library, which is not exposed to the external client.

The fix for CVE has been resolved in version 2.1.1 release which is included in spring-boot-data-jpa 2.1.0.RELEASE.

Request Exception.

To fix this would require upgrading spring-boot version to 2.1.0-RELEASE

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-397

...