1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
.TH "CVE REJECT" "1" "2024-12-06" "1.7.1" "cve reject Manual"
.SH NAME
cve\-reject \- Reject a CVE record for a reserved or...
.SH SYNOPSIS
.B cve reject
[OPTIONS] CVE_ID
.SH DESCRIPTION
Reject a CVE record for a reserved or published CVE ID.
.PP
If the CVE is already rejected, this action will update its record if one is supplied.
A rejected CVE with a record can only be moved to the published state (see `cve publish`).
A rejected CVE without a record can be moved to the reserved state. A published CVE can only
be rejected with an accompanying record. Reserved CVEs can be rejected with or without a record.
.PP
Note: Rejecting a published CVE removes both the CNA and ADP data of that record.
.PP
The CVE reject record can be specified as a string:
.PP
cve reject CVE-2022-1234 -j '{"rejectedReasons": [{"lang": "en", "value": "A reason."}]}'
.PP
Or passed in a file:
.PP
cve reject CVE-2022-1234 -f v5_reject_record.json
.PP
For information on the required properties in a given CVE JSON record, see the schema in:
.PP
https://cveproject.github.io/cve-schema/schema/docs/
.PP
Because the CVE Services API only expects the cnaRejectedContainer contents of the full record,
the record you pass to this command can specify just that data, and not the full record.
.PP
.SH OPTIONS
.TP
\fB\-j,\fP \-\-cve\-json TEXT
JSON body of CVE record to reject.
.TP
\fB\-f,\fP \-\-cve\-json\-file FILENAME
File containing JSON body of CVE record to reject.
.TP
\fB\-\-raw\fP
Print response JSON.
|
