Skip to content
This repository was archived by the owner on Jul 24, 2021. It is now read-only.
This repository was archived by the owner on Jul 24, 2021. It is now read-only.

Add NVD as a source #2

Description

@rtfpessoa

NVD is one of the best sources for vulnerabilities. The only issue to support it is that the information it provides is not very well structured to be used by us, specially the package names that each CVE refers to.

I think we can kind of overcome this with:

  • Download all the compressed packages with CVEs since forever
  • Load all our current database
  • Use the current database to reverse engineer the names of the packages in the NVD database based on the name we have for them and the CVEs we know are related to them
  • Create a mapping of names from NVD to our database
  • Search NVD for vulnerabilities using the mappings
  • (Crazy idea) We could also search NVD for vulnerabilities a similarity match of our name with theirs if we don't have a mapping

Notes/Help:

This is a very exploratory task and the results need to be evaluated and checked since this might bring a lot of weird results due to the complicated matching.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    HacktoberfestEntry level issues for https://hacktoberfest.digitalocean.com/help wantedinvestigationExploratory tasks, usually to introduce new features

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions