Incorrect Product Status in Software Vulnerability Manager

Incorrect Product Status in Software Vulnerability Manager

Summary 

The customer faces an issue where the product status in Software Vulnerability Manager is incorrect. 

Cause

  • The product detection rule is not available in the product vulnerability database.
  • Vulnerability Database hasn't been synced with Flexera SVM backend

Diagnoses

  1. The product detection rule is not available in the product vulnerability database.
  • Login to the SVM database

           MySQL -u root -p

  • Select the Vulnerability Database

           Use vuln_track;

  • Execute this command to check the os_soft_id in the Vulnerability database

         SELECT os_soft_id FROM os_soft WHERE os_soft_name LIKE 'put product name here';

  • Use the os_soft_id as product ID in the below command to check the detection rule.

          SELECT * FROM vuln_track.sr_match_files WHERE product_id =put product ID here;

Please note:
If the above query doesn’t provide a result, this means the product detection rule is not available in the vulnerability database for tracking and issuing an advisory.

  1. Vulnerability Database hasn't been synced with Flexera SVM backend
  • Login to the SVM database

           MySQL -u root -p

  • Select the Vulnerability Database

          Use vuln_track;

  • Execute this command to check the product ID in the Vulnerability database

         select MAX(vuln_create_date) from vuln_track.vuln;

Please note:
If the above query doesn’t provide a current date and shows an old date, this means the Vulnerability Database hasn’t been synced.

https://community.flexera.com/t5/Software-Vulnerability-Manager/Coffee-Break-Series-1-Checking-the-V...


Solution

 
Product detection rule is not available.


The customer needs to suggest the software via his SVM cloud portal, so the Flexera File Signature team can add the product to the database for tracking and detection rule.

SVM > Configuration > Suggest Software

raslam_0-1606735886989.png

 

Vulnerability Database hasn't been synced with Flexera SVM backend

  • Check your SVM onpremise server public IP

If the public IP has been changed and Flexera SVM backend whitelisted public IP is old then the Vulnerability database will not get the latest vulnerability information

  • Tail the /usr/local/Secunia/csi/log/sync.log for any errors etc

    tail -n 1000 /usr/local/Secunia/csi/log/sync.log

    If you see errors in the sync log or the public IP has been changed, then please contact Flexera SVM support.

    Important:  The SVM on-premise customers cant suggest the software from their SVM portal via IE, so they need to request SVM support to provide them the SVM cloud account with one host license, so they can suggest the software. 

 

 

Was this article helpful? Yes No
No ratings
Version history
Revision #:
7 of 9
Last update:
‎Dec 01, 2020 03:21 AM
Updated by:
 
Contributors