[go: nahoru, domu]
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.

Sign up for GitHub

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

Jump to bottom

no RESERVED CVEs #38

Open
pth-one opened this issue Oct 13, 2023 · 2 comments
Open

no RESERVED CVEs #38

pth-one opened this issue Oct 13, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@pth-one
Copy link
pth-one commented Oct 13, 2023

if attempting to use this repository as a definitive source of CVEs then it seems having those that have been reserved would be useful but are not currently available.
For example, right now CVE-2023-38545 exists in the cvelist repository... but not cvelistV5
@hkong-mitre hkong-mitre added the enhancement New feature or request label Nov 12, 2023
@JonathanLEvans
Copy link

There isn't a schema for reserved records in 5.x. See CVEProject/cve-schema#126 for the decision.

@phi-go
Copy link
phi-go commented Apr 23, 2024

As far as I can see CVEProject/cve-schema#126 does not contain a reason for the decision, indeed there is an extensive comment describing why RESERVED CVEs should be available. However, it seems that comment was ignored.

Is there a plan to provide a "definite source of CVEs" in this repo? Especially as the "legacy" versions will be phased out according to the website.

Please excuse my negativity, I'm a bit confused on what the direction is.

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

No branches or pull requests
4 participants
@phi-go @hkong-mitre @pth-one @JonathanLEvans