Versions Compared

Key

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

...

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.

Tip
titleUsage

Please make a Copy of this template into your project wiki space. Be sure to make a Copy (not a Move) by using the ... on the top right corner of this 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


The following table is addressing 2 different scenarios:

...

Not applicable
RepositoryGroupImpact AnalysisAction
aaf-authz-dockercom.thoughtworks.xstreamQ-How does this vulnerability impact your project

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

clampcom.fasterxml.jackson.coreFalse positive

N/A

clampangular


Jira:
clamp angular Jira:
clamporg.apache.tomcat.embed   Jira:
clamp org.apache.tomcat.embed   
 clamp jquery  
clamp org.glassfish.grizzly :grizzly-http  
clamp org.webjars.npm bootstrap    
clamp com.sun.faces : jsf-impl    
clampjquery   
clamp angular   
clamp com.sun.faces : jsf-impl    
clamp  org.jboss.resteasy : resteasy-jaxrs