Versions Compared

Key

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

...

RepositoryGroupImpact AnalysisAction
dmaap-messagerouter-msgrtrcom.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-msgrtrjavax.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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDMAAP-785


dmaap-messagerouter-messageservicecom.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-messageservicejavax.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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDMAAP-785

dmaap-messagerouter-messageserviceorg.springframework.security.oauthThis component is comping from the ajsc libraries. DMaaP don’t have the oAuth functionality, so it will not impactNo action required. Requesting an exception
dmaap-messagerouter-messageserviceorg.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-messageserviceorg.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-messageservicecommons-fileupload This component is comping from the ajsc libraries. DMaaP don’t have file upload functionality. So DMaaP is not vulnerableNo action required. Requesting an exception
dmaap-messagerouter-dmaapclientcom.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-datarouter-provcom.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-dmaapclientcom.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

...