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 the TSC at Code Freeze milestone (M4).
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.
In the case where you have nested third party components (a third party component embedding another third party component) and there is NO CVE number for the upstream third party component (meaning the third party component you are embedding), it is recommended to open a vulnerability issue on the upstream third party component.
The following table is addressing 2 different scenarios:
- Confirmation of a vulnerability including an action
- False Positive
The information related to Repository and Group are extracted from the CLM report.
...
JIRA Link
In the JIRA ticket, you will explain findings and action plan
Add the Label "Security"
...
False Positive
Add the explanation why you believe it is a false positive
...
table represents the known exploitable and non-exploitable vulnerabilities in third party packages used in the project
| Repository | Group | Impact Analysis | Action | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| dmaap-messagerouter-msgrtr | com.fasterxml.jackson.core | There is no non vulnerable version of this component(jackson-databind-2.8.11.1).This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization. DMaaP MR don't use the default typing. False Positive | No action required. Requesting an exception for all the issues reported due to this component https://jira.onap.org/browse/DMAAP-784 | ||||||||
| dmaap-messagerouter-msgrtr | javax.mail | Message-Id in the email contains the user name and host name of the java process that triggered the email This component is coming from the Cambria library and all of its versions are vulnerable. As of today non of the Message Router clients use the email generating functionality of the Message Router. False Positive | No action required. Requesting an exception
| ||||||||
| dmaap-messagerouter-messageservice | com.fasterxml.jackson.core | There is no non vulnerable version of this component(jackson-databind-2.8.11.1).This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization. DMaaP MR don't use the default typing. False Positive | No action required. Requesting an exception for all the issues reported due to this component | ||||||||
| dmaap-messagerouter-messageservice | javax.mail | Message-Id in the email contains the user name and host name of the java process that triggered the email This component is coming from the Cambria library and all of its versions are vulnerable. As of today non of the Message Router clients use the email generating functionality of the Message Router. False Positive | No action required. Requesting an exception
| ||||||||
| dmaap-messagerouter-messageservice | org.springframework.security.oauth | This component is comping from the ajsc libraries. DMaaP don’t have the oAuth functionality, so it will not impact | No action required. Requesting an exception | ||||||||
| dmaap-messagerouter-messageservice | org.apache.camel | This component is comping from the ajsc libraries. DMaaP don’t use the file attachment in email. So this vulnerability don't impact DMaaP. | No action required. Requesting an exception | ||||||||
| dmaap-messagerouter-messageservice | org.springframework | This component is comping from the ajsc libraries. DMaaP is a REST project and don’t serve any static resources. So this vulnerability don't impact DMaaP. | No action required. Requesting an exception | ||||||||
| dmaap-messagerouter-messageservice | commons-fileupload | This component is comping from the ajsc libraries. DMaaP don’t have file upload functionality. So DMaaP is not vulnerable | No action required. Requesting an exception | ||||||||
| dmaap-messagerouter-dmaapclient | com.fasterxml.jackson.core | There is no non vulnerable version of this component(jackson-databind-2.8.11.1).This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization. DMaaP MR don't use the default typing. False Positive | No action required. Requesting an exception for all the issues reported due to this component | ||||||||
| dmaap-datarouter-prov | com.h2database : h2 | There is no non vulnerable version of this component(com.h2database : h2 : 1.4.197).This is only used to mock the database in unit tests False Positive | No action required. Requesting an exception for all the issues reported due to this component | ||||||||
| dmaap-messagerouter-dmaapclient | com.att.nsa : dmaapClient | Component com.att.nsa:dmaapClient was not used in the project dmaap-messagerouter-dmaapclient. these issues are due to issues in CLM Scan False Positive | Created a LF ticket #54030,54268 . LF Help desk updated that they don't know why the scan reported these vulnerabilities |
Note:
1) dmaap-messagerouter-docker and dmaap-buscontroller projects are created for releasing the docker images. Vulnerabilities reported in these projects are duplicate of dmaap-messagerouter-messageservice and dmaap-dbcapi