Please add Vulners as a source

[jvoisin]

As mentionned in this issue, it would be nice to integrate Vulners as a source.

[PidgeyL]

do you have a link to a file we can parse to get this info?

[jvoisin]

Sure, as stated by @vulnersCom:

Yes, it is available for download.
Feel free to bundle it.
All dataset is separated by "types".
You can download whole dataset of the "type" in JSON using this call:

https://vulners.com/api/v3/archive/collection/?type=cve
https://vulners.com/api/v3/archive/collection/?type=exploitdb
https://vulners.com/api/v3/archive/collection/?type=centos

And so on. Check possible "type" values by this call:
https://vulners.com/api/v3/search/suggest/?fieldName=type&type=distinct

To make a good linkage to CVE check "cvelist" key. It holds link to the CVE for each element.
For better correlation you may integrate this online calls:

Search all data for CVE:
https://vulners.com/api/v3/search/lucene?query=cvelist:CVE-2014-0160
Abstract vulnerability search:
https://vulners.com/api/v3/search/lucene?query=Your_cool_query
Data for element + dynamic references search:
https://vulners.com/api/v3/search/id/?id=CVE-2014-0160&references=True

P.S.
Search query syntax and examples are here:
https://vulners.com/help

[adulau]

@jvoisin thanks for the reminder ;-)

[vulnersCom]

One more reminder?))

[CriimBow]

I also think it would be beneficial to integrate Vulners into VIA4CVE.
But, in my opinion, we should not import directly Vulners but import vulners by "type" like it is already done with Metasploit.
This way, if one day Vulners is KO, we can resume module by module and even if the workload remains high, the tasks will already be divided by sources.