aboutcode-org / aboutcode-org/vulnerablecode

Add date of publishing in vulnerability detail view

Open
#1,355 3 comments 0 reactions 2 assignees Claimed by @TG1999 View on GitHub
Dominant language
Python
Stars
702
Forks
328
Avg merge
3d 8h
Merged PRs (30d)
3

Description

ATM in VCIO a vulnerability is an object created by the culmination of multiple advisories. We will use the NVD importer publish date as default for each vulnerability, in case an advisory from the NVD is not being used in that vulnerability we will use the most oldest publishing date from other importers' advisory.

Ways to achieve this:

- 1.) Store two DateTime fields in the vulnerability model, `nvd_published_date` and `latest_published_date`. We will populate `nvd_published_date` with the date/time of the NVD advisory publishing date and and `latest_published_date` will be keep changing as new advisories add any data in the Vulnerability, if we have `nvd_published_date` for a vulnerability we will always use it as a default date.

- 2.) For every vulnerability, get a list of advisories that have the aliases of that vulnerability. If any advisory from that list is from the NVD use that date otherwise use the oldest date of publish among those advisories

- 3.) Store a list of advisories that are used in the creation of that vulnerability in the Vulnerability model and compute the date of publish from that list of advisories. If any advisory from that list is from the NVD use that otherwise use the oldest date of publish among those advisories

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.