fix:Duplicated EPSS data in database

[anthonyharrison]

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.

[anthonyharrison]

Typo in line 114 should be PRIMARY KEY (cve_number, metric_id), (NOTE the ',' !!!!)

[vedantexists]

Hi, I'm a first-time contributor and would love to work on this issue. Could you assign it to me? I'll have a fix ready soon.

[anthonyharrison]

Hi, I'm a first-time contributor and would love to work on this issue. Could you assign it to me? I'll have a fix ready soon.

No need to be assigned - just create the pull request and wait for the feedback.

As a first time contributor, read the guides on getting started and ensure that you can get a local copy of the tool working. There may need to be a test added to simply demonstrate that adding two EPSS entries for the same CVE only results in one entry in the table.

[vedantexists]

@anthonyharrison Hi, just checking in on this PR. Happy to make any changes if needed. Let me know if there's anything I can improve!