- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
10-24-2024 08:15 PM - edited 10-24-2024 08:19 PM
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
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!