Confirm that importers filter out CVE Status "REJECT" and NVD Status "Rejected"

[DennisClark]

Please refer to https://nvd.nist.gov/vuln/vulnerability-status

In the "CVE List Statuses" table, note:
REJECT | ... As a rule, REJECT CVE Entries should be ignored.

In the "NVD Statuses" table, note:
Rejected | CVE has been marked as "**REJECT**" in the CVE List. These CVEs are stored in the NVD, but do not show up in search results.

Both Statuses are essentially "noise" and it seems that the associated CVE/NVD's should not be selected for VulnerableCode data, since they are only a distraction and add no value to VulnerableCode.

If VC is already filtering such entries out, please simply confirm and close this issue; otherwise, please improve the importers (and possibly the improvers) to filter them out.

[mjherzog]

Since the NVD and others keep these records we probably need to also keep a record but show the status much more clearly.
Using VCID-zzsb-14xc-aaam as an example;

• Status=Invalid should override data for Exploitability, Weighted Severity and Risk because these values are also invalid in context.
• We just need a reference record that this CVE / GHSA exists and is invalid.
• The references to https://github.com/dom4j/ and https://github.com/joker-xiaoyan/ are inscrutable - I cannot see any reference to the Vuln at these URLs.