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.
...
table represents the known exploitable and non-exploitable vulnerabilities in third party packages used in the project
| Repository | Group | Impact Analysis | Action | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| clamp | com.fasterxml.jackson.core | False positive, we have added
|
| |||||||||||
| clamp | angular | We can't remove angular because it requires a complete re-write of the UI. Anyway we have mitigated the issue by setting the angular version to 1.3.2 with the least amount of security issue | Jira: | |||||||||||
| clamp | angular | We can't remove angular because it requires a complete re-write of the UI. But we have chosen the angular version with the least amount of security issue | Jira: | |||||||||||
| clamp | angular | We can't remove angular because it requires a complete re-write of the UI. But we have chosen the angular version with the least amount of security issue | ||||||||||||
| clamp | angular | We can't remove angular because it requires a complete re-write of the UI. But we have chosen the angular version with the least amount of security issue | ||||||||||||
| clamp | angular | We can't remove angular because it requires a complete re-write of the UI. But we have chosen the angular version with the least amount of security issue | ||||||||||||
| clamp | angular | We can't remove angular because it requires a complete re-write of the UI. But we have chosen the angular version with the least amount of security issue | reported by Nexus IQ (for Release 1.XX) | Analyze how to migrate the UI to a recent angular version (> 4.X)
| ||||||||||
| clamp | bootstrap | It impacts our UI as bootstrap (one of the latest version, 4.1.1) is used in clamp code. We could be impacted by the possible Cross-Site Scripting (XSS) reported by Nexus IQ | bootstrap library 4.1.3 CLAMP is using, doesn't present a vulnerability anymore
|