CVEProject / cve-schema

This repository is used for the development of the CVE JSON record format. Releases of the CVE JSON record format will also be published here. This repository is managed by the CVE Quality Working Group.

CVEProject/cve-schema Issues

original assigner vs. owner
Updated 2 months ago3
ADP content update bumps the date for the CVE record
Updated 2 months ago
Clarify date fields
Updated 2 months ago
Three dateUpdated fields, all set by Services
Updated 2 months ago1
Relax format restrictions on programFiles
Closed 2 months ago2
Max length of 4096 for description is too limiting
Closed 2 months ago2
Use UTC instead of GMT in JSON5
Updated 2 months ago
I'm
Updated 2 months ago
5.1.0 defines datestamp but doesn't use it
Updated 2 months ago
Sync with upstream CVSS v4 bug fixes.
Updated 3 months ago
Versions listed here do not match `versions` list, so probably not a great example of what to do.
Closed 3 months ago
f
Closed 3 months ago
5.1.0 allows use of versionType git without a repo field
Updated 3 months ago
5.1.0 accepts versionType git without a Git commit hash
Updated 3 months ago
full-record-advanced-example.json Does Not Contain A Tags Field
Updated 3 months ago
Vulnerability Type: Configuration
Updated 3 months ago
v5.1.0-rc2 has two instances of "cve.mitre.org"
Updated 4 months ago
v5.1.0-rc2 $id contains v5.0
Updated 4 months ago
missing type "object" for 5.1.0-rc2 container subschemas
Updated 4 months ago
5.1.0 accepts language of "eng" (instead of "en") in most places
Updated 4 months ago3
5.1.0 accepts user UUIDs even though User Registry doesn't exist
Updated 5 months ago4
5.1.0 accepts multiple versions for a single status change
Updated 5 months ago
versions.md misuses 1.0 in a semver example
Updated 5 months ago
5.1.0 accepts versionType semver for non-semver lessThan
Updated 5 months ago
5.1.0 accepts versionType semver for non-semver data
Updated 5 months ago
5.1.0 accepts an object (instead of a string) for source.discovery
Updated 5 months ago
5.1.0 accepts undefined properties under "affected"
Updated 5 months ago
5.1 incompatible with /containers/cna/metrics/*/other/version ?
Updated 6 months ago5
Retire CVSS 2.0 & 3.0 in Schema 5.0.1
Closed 6 months ago6
dataVersion "enum": ["5.1"] breaks backward compatibility
Closed 6 months ago8
Add support for CVSS 4.0
Closed 7 months ago5
additionalProperties is needed in other places to prevent stray field names
Closed a year ago7
CVSS v3.1 schema allows undefined field names (e.g., extra whitespace)
Closed a year ago1
CVE v5 Schema $id returns a 404
Closed 10 months ago5
Indicate constraints on using $ and . in object field names
Closed a year ago1
Prevent descriptions from containing only whitespace
Updated 8 months ago5
confusion about ssZZZZ in date-time format
Updated 8 months ago
add a "research-advisory" or similar tag
Updated 8 months ago
Create a best practices of the CVE JSON usage
Updated 9 months ago20
stray additionalProperties line in 5.0.1
Updated 9 months ago
CVE Records that don't comply with 5.0.1
Updated 9 months ago
Allowed Characters in Descriptions and Workarounds
Closed 10 months ago1
taxonomyMappings is still missing a description
Closed 10 months ago1
taxonomyRelations is still missing a description
Closed 10 months ago1
Create examples for cnaContainer JSON
Closed a year ago2
---- de
Closed a year ago1
x_ usage interferes with some JSON applications
Closed a year ago1
Add new type for credits
Closed a year ago1
cannot specify that a range includes at least one affected version
Updated a year ago2
Reserved but Public (RBP) records block ADPs from contributing to a CVE record until it is published.
Updated a year ago