Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate and warn if datePublic is in the future #118

Closed
zmanion opened this issue Jul 11, 2023 · 3 comments
Closed

Validate and warn if datePublic is in the future #118

zmanion opened this issue Jul 11, 2023 · 3 comments

Comments

@zmanion
Copy link
Contributor

zmanion commented Jul 11, 2023

Discussed on the 2023-07-11 AWG call, datePublic is an optional field set by the CNA. It seems that at least once, a CNA thought that datePublic controlled when the CVE record would be published. The CVE record is published the moment the CNA submits the record content to the services.

We should review and if necessary improve the documentation for datePublic.

Should the services check datePublic, and if it is set in the future, refuse to accept the submission and return an error message?

@zmanion
Copy link
Contributor Author

zmanion commented Jul 12, 2023

Restating: datePublic should never be later than datePublished, as publishing in CVE makes the vulnerability public.

@zmanion
Copy link
Contributor Author

zmanion commented Mar 18, 2024

Proposal: Services checks datePublic if set, if in future, return error and do not publish CVE Record.

@mprpic
Copy link
Collaborator

mprpic commented Apr 3, 2024

This was actually already addressed in CVE Services: CVEProject/cve-services#1097 . Closing!

@mprpic mprpic closed this as completed Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants