Support Rejected -> Published

[zmanion]

Support Rejected -> Published

[openmorse]

@zmanion - that seems a correct summary.

CVE Services allows updating CVE Records from REJECTED to PUBLISHED.

However, Vulnogram does not allow it in at least one use case:

• From the displayed list of the user's REJECTED CVE Records,
• Select an existing REJECTED CVE ID to prepopulate the data fields
• Attempting to update will result in error

Workaround described by zmanion above.

[zmanion]

RESERVED -> REJECTED is permitted by Services and supported by Vulnogram. Such an ID cannot be un-REJECTED or, at least using Vulnogram, Services returns CVE_RECORD_DNE. It is not possible to modify the Record ("Rejected Reason"), there is no Record at all (Services returns 404 for the /cve/ endpoint).

https://cveawg-test.mitre.org/api/cve/CVE-2024-20642

PUBLISHED -> REJECTED is permitted by Services and supported by Vulnogram. Such an ID/Record can be un-REJECTED. In Vulnogram, you need to create a new record, re-populate it, and publish.

So, I now dont' think this is a bug in Vulnogram, and probably doesn't require any action or change to Vulnogram.

Loading a REJECTED (but previously published) Record can only possiby load the current Record data, which includes the rejectedReasons element.

[zmanion]

OK, maybe an enhancement then.

In the view of Rejected IDs, indicate which exist as Records (had previously been Published), and provide an "unreject" or "re-edit" button or icon (maybe a green check mark in the Actions column).

On click, load a new (CNA container) editor screen (equivalent to clicking the NEW button) with the (rejected, about to be republished) CVE-ID populated.