10-30-2024 08:43 AM
@assubramania, this happens because the NVD command !nvd-search-cve is not a reputation command but rather a CVE lookup command. One way to map the metrics output from the command !nvd-search-cve to your CVE type indicator is to create an indicator field of type Grid, containing all the columns that are part of the metrics result (see screenshot), associate it to the CVE indicator type, and then set the grid with the values from that output in a different task in your playbook. To populate the grid you can use the automation attached (SetGridField4Indicator). Lastly, in order to display the new field in your CVE indicator layout, you need to edit the layout to include it (see screenshots "CVE Indicator layout.png" and "CVE Indicator View.png")
This is the syntax to use the command attached:
!SetGridField4Indicator grid_id=cvemetrics columns="CVSS Vector String,CVSS Integrity Impact,CVSS Scope,CVSS Attack Complexity,CVSS User Interaction,CVSS Confidentiality Impact,CVSS Attack Vector,CVSS Privileges Required,CVSS Base Score,Exploitability Score,Impact Score,CVSS Availability Impact,CVSS Base Severity" context_path=NistNVD.CVESearch.metrics indicator=CVE-2024-10154
