Closed szymonpk closed 5 years ago
Hi @szymonpk ,
You are right but I don't know why the CVE-2018-15727
is tagged in a different way into the NVD vulnerabilities file and therefore, the parser I have implemented for CVEs doesn't recognice that CVE.
On the other hand, the error you get in the log is related on Sysdig Falco and the monitoring feature. Perhaps, when Dagda tries to shut down the previous Falco container, it found multiple container with similar IDs. I'm not sure about it because is a very rare issue. How many times do you get this error in the logs?
Is summary the only difference? The one you have pasted is from CVE-2018-558213
which was a candidate for proper CVE CVE-2018-15727
, probably there are more records like this.
If there is any issue in the parser which filters the NVD files, it would be in the next function:
Hi @szymonpk ,
Did you found any error in the parser of the NVD files for fixing your issue? Could you give me any update you have about this issue?
Sorry but no. I couldn't find time for this.
Closed due to inactivity.
Short description
I am trying to request information with dagda about CVE-2018-15727 which is present in securityfocus and NVD databases and I am getting "CVE not found"
Reproduction steps
docker-compose up
python dagda.py vuln --init
and wait until it is finished.python dagda.py vuln --cve CVE-2018-15727
Expected results
I expected information about CVE. I can get information about other CVE's just fine. For example:
Actual results
On which platforms did you notice this:
Backtrace
During startup I have noticed:
But application works fine(-ish), there is no errors when querying for CVE's