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
|
.TH "CVE PUBLISH" "1" "2024-12-06" "1.7.1" "cve publish Manual"
.SH NAME
cve\-publish \- Publish a CNA container of a CVE record...
.SH SYNOPSIS
.B cve publish
[OPTIONS] CVE_ID
.SH DESCRIPTION
Publish a CNA container of a CVE record for a reserved (or rejected) CVE ID.
.PP
If the CVE is already published, this action will update the CNA container in its record. A
published CVE can only be moved to the rejected state with an appropriate reject record (see
`cve reject`). A published CVE cannot be moved back to the reserved state.
.PP
The CNA container can be specified as a string:
.PP
cve publish CVE-2022-1234 -j '{"affected": [], "descriptions": [], "references": {}, ...}'
.PP
Or passed in a file:
.PP
cve publish CVE-2022-1234 -f cve.json
.PP
For information on the required properties in a given CNA container of a CVE record,
see the schema in:
.PP
https://cveproject.github.io/cve-schema/schema/docs/
.PP
Because the CVE Services API only expects the CNA container contents of the full CVE v5 record,
the data you pass to this command can specify just the attributes defined by the
cnaPublishedContainer or cnaRejectedContainer subschemas, and not the full schema record.
.PP
.SH OPTIONS
.TP
\fB\-j,\fP \-\-cve\-json TEXT
JSON body of CVE record to publish.
.TP
\fB\-f,\fP \-\-cve\-json\-file FILENAME
File containing JSON body of CVE record to publish.
.TP
\fB\-\-raw\fP
Print response JSON.
|
