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.
| Repository | Group | Impact Analysis | Action |
|---|---|---|---|
| clamp | com.fasterxml.jackson.core | False positive, we have added unit test to ensure the code is secure(it doesn't trigger the unsecure path) | N/A |
| clamp | angular | We can't remove angular because it requires a complete re-write of the UI. | CLAMP-223 - Getting issue details... STATUS |
| clamp | bootstrap | We can't remove bootstrap because it requires a complete re-write of the UI. But we have chosen the version with the least amount of security issue | CLAMP-223 - Getting issue details... STATUS |