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

Support CVE ID assignment using CVE Program services #8

Closed
zmanion opened this issue Feb 15, 2021 · 3 comments
Closed

Support CVE ID assignment using CVE Program services #8

zmanion opened this issue Feb 15, 2021 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@zmanion
Copy link
Contributor

zmanion commented Feb 15, 2021

VINCE should support CVE ID assignment, including pool management for a CNA, using the developing CVE Program services (e.g., authentication and IDR).

https://github.com/CVEProject/cve-services/wiki/Developer-Guide-to-CVE-Services-API

https://github.com/RedHatProductSecurity/cvelib

@zmanion
Copy link
Contributor Author

zmanion commented Feb 15, 2021

Note: VINCE currently can generate CVE JSON, a future request will be to integrate CVE ID submission to whatever appropriate service, which may or may not be the IDR.

@zmanion zmanion added the enhancement New feature or request label Feb 15, 2021
@zmanion zmanion assigned zmanion, sei-eecoff and madcatter24 and unassigned zmanion Feb 15, 2021
@zmanion
Copy link
Contributor Author

zmanion commented Feb 7, 2022

Probably use this, which currently supports some user/org management and CVE ID management and requests (but not yet submitting CVE IDs, which the services don't support yet either).

https://github.com/RedHatProductSecurity/cvelib

@zmanion
Copy link
Contributor Author

zmanion commented Feb 7, 2022

Possibly sub-issues:

  1. Manage CNA/organization and users, API keys
  2. Request CVE IDs, probably in the vulnerability UI in a case
  3. Track/report/manage requested and assigned CVE IDs
  4. Publish/post/submit CVE IDs, probably in or near the vulnerability note UI, but independent of publishing the vulnerability note

4 will require collecting and verifying minimum required information for a valid CVE entry. Description can come from existing vulnerability description field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants