Description
The size of the databases is growing due to the EPSS entries for the vulnerabilities. This is becuase there are multiple EPSS entries for each CVE, there should only be one (the latest) for each CVE
To reproduce
Update the database with the latest data. Examibne the database and the number of EPSS entries for each CVE will have increased
Expected behaviour:
A single EPSS values for each vulnerability
Actual behaviour:
Multiple EPSS entries for each vulnerability
Version/platform info
Version 3.4.1
Anything else?
The issue is with the insertion of the data using a INSERT or UPDATEoperation.
The impact is that the retrieval of the EPSS value for the CVE returns multiple values which increases the processing time.
Description
The size of the databases is growing due to the EPSS entries for the vulnerabilities. This is becuase there are multiple EPSS entries for each CVE, there should only be one (the latest) for each CVE
To reproduce
Update the database with the latest data. Examibne the database and the number of EPSS entries for each CVE will have increased
Expected behaviour:
A single EPSS values for each vulnerability
Actual behaviour:
Multiple EPSS entries for each vulnerability
Version/platform info
Version 3.4.1
Anything else?
The issue is with the insertion of the data using a INSERT or UPDATEoperation.
The impact is that the retrieval of the EPSS value for the CVE returns multiple values which increases the processing time.