You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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.

RepositoryGroupImpact AnalysisAction
clampcom.fasterxml.jackson.core

From NexusIQ:

"jackson-databind is vulnerable to Remote Code Execution (RCE). The createBeanDeserializer() function in the BeanDeserializerFactory class allows untrusted Java objects to be deserialized. A remote attacker can exploit this by uploading a malicious serialized object that will result in RCE if the application attempts to deserialize it."


  • We have added a Jackson wrapper that must be used in the code, it disables the incriminated feature. We have also added a unit test to ensure the code is secure.
  • We will change that library and replace it by another one (GSON)

CLAMP-236 - Getting issue details... STATUS

clampangular

It impacts our UI as angular is the skeleton technology used in the code.

Anyway we have mitigated the issue by setting the angular version to 1.3.2 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-223 - Getting issue details... STATUS

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

Wait until Bootstrap library is fixed or investigate how to delete/replace it

CLAMP-237 - Getting issue details... STATUS



  • No labels