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.
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.
...
| title | Usage |
|---|
...
page
...
Within the M4 checklist create a link toward your copy of this template
Once this template has been copied into your project wiki space, you can delete this "Tip" section as well as the "Sample of CLM Report" screenshot. This screenshot is just an example.
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)
...
False Positive
Explaination: This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization.
msb-apigateway doesn't invoke this method, and a concrete java type is explicitly specified when deserializing the JSON objects, so this vulnerability issue has no impact on msb-apigateway.
https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization
msb-apigateway codes using ObjectMapper:
...
False Positive
Explaination: This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization.
msb-apigateway doesn't invoke this method, and a concrete java type is explicitly specified when deserializing the JSON objects, so this vulnerability issue has no impact on msb-apigateway.
https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization
msb-apigateway codes using ObjectMapper:
...
False Positive
Explaination: This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization.
msb-apigateway doesn't invoke this method, and a concrete java type is explicitly specified when deserializing the JSON objects, so this vulnerability issue has no impact on msb-apigateway.
https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization
msb-apigateway codes using ObjectMapper:
...
This vulnerability issue is an indirect dependency introduced by msb-swagger-sdk, which is a false positive.
msb-apigateway doesn't use Common-collection lib in its codes.
...
This vulnerability issue is an indirect dependency introduced by msb-swagger-sdk, which is a false positive.
msb-apigateway doesn't use Common-collection lib in its codes.
...
This vulnerability issue is an indirect dependency introduced by msb-swagger-sdk, which is a false positive.
msb-apigateway doesn't use Common-collection lib in its codes.
...
False Positive
Explanation: This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization.
msb-discovery doesn't invoke this method, and a concrete java type is explicitly specified when deserializing the JSON objects, so this vulnerability issue has no impact on msb-discovery.
https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization
msb-discovery codes using ObjectMapper:
...
False Positive
Explanation: This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization.
msb-discovery doesn't invoke this method, and a concrete java type is explicitly specified when deserializing the JSON objects, so this vulnerability issue has no impact on msb-discovery.
https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization
msb-discovery codes using ObjectMapper:
...
False Positive
Explanation: This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization.
msb-discovery doesn't invoke this method, and a concrete java type is explicitly specified when deserializing the JSON objects, so this vulnerability issue has no impact on msb-discovery.
https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization
msb-discovery codes using ObjectMapper:
...
False Positive
Explanation:
This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization.
msb-discovery doesn't invoke this method, and a concrete java type is explicitly specified when deserializing the JSON objects, so this vulnerability issue has no impact on msb-discovery.
https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization
msb-java-sdk codes using ObjectMapper:
...
False Positive
Explanation:
This vulnerability issue only exists if com.fasterxml.jackson.databind.ObjectMapper.setDefaultTyping() is called before it is used for deserialization.
msb-discovery doesn't invoke this method, and a concrete java type is explicitly specified when deserializing the JSON objects, so this vulnerability issue has no impact on msb-discovery.
https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization
msb-java-sdk codes using ObjectMapper:
...
msb-swagger-sdk
...
False Positive
It does not cause any issues to the services and service does not expose functionality directly
...
False Positive
It does not cause any issues to the services and service does not expose functionality directly
...
False Positive
It does not cause any issues to the services and service does not expose functionality directly
...
False Positive
It does not cause any issues to the services and service does not expose functionality directly
...
False Positive
It does not cause any issues to the services and service does not expose functionality directly
...
has been moved to R3 MSB Security/Vulnerability Threat Impact Analysis