You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Discrepancy between v4.0 .schema file and DRAFT markdown document #2
After reviewing the CVE_JSON_4.0_min_public.schema JSON Schema definition and then reading the DRAFT-JSON-file-format-v4.md document, I noticed that the .schema file was missing many of the keys/Objects described in DRAFT-JSON-file-format-v4.md (ex: configuration, impact, version_affected). Is this intentional or a mistake? Is CVE_JSON_4.0_min_public.schema intended to be a minimal subset of the CVE v4.0 JSON Schema? If so, does a complete JSON Schema definition file exist for CVE v4.0?
Version 4 was experimental for the github submission pilot. Some keys you cited were never defined and left to interpretation.
These fields/keys have been now defined in version 5 schema. There are no plans to port them to version 4 schema.
@chandanbn just to get some clarification, when version 5 is finalized, will the cvelist github repository be upgraded to use only version 5 JSON schema? Or will cvelist contain both version 4 and version 5 JSON data?
Activity
chandanbn commentedon Apr 1, 2021
Version 4 was experimental for the github submission pilot. Some keys you cited were never defined and left to interpretation.
These fields/keys have been now defined in version 5 schema. There are no plans to port them to version 4 schema.
postmodern commentedon Apr 5, 2021
@chandanbn just to get some clarification, when version 5 is finalized, will the cvelist github repository be upgraded to use only version 5 JSON schema? Or will cvelist contain both version 4 and version 5 JSON data?
chore: Use RFD CVEProject#2