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

Allow non-vendor CNAs to provide "affects" data #12

Open
zmanion opened this issue Oct 20, 2022 · 0 comments
Open

Allow non-vendor CNAs to provide "affects" data #12

zmanion opened this issue Oct 20, 2022 · 0 comments

Comments

@zmanion
Copy link
Contributor

zmanion commented Oct 20, 2022

When vendor CNAs provide information about affected products, that information is included in published entries.

When CNAs or other parties who are not vendor CNAs submit entries, any product information is stripped and replaced with "n/a." In JSON 4 this includes fields like version_value, version_affected, product_name, vendor_name within the "affects" element. Also problemtype is stripped.

I was concerned this was some sort of bug, it is intentional behavior.

An example:

Product information submitted by non-vendor: CVEProject/cvelist@4f7a575

Product and problem type information is removed:
CVEProject/cvelist@7fcef33

https://github.com/CVEProject/cvelist/commits/master/2022/24xxx/CVE-2022-24106.json

CVEProject/cvelist#7712

Presumably past discussion lead to this policy decision, a likely concern was that non-vendor CNAs would (intentionally or otherwise) provide enough inaccurate information that on the balance, this would negatively affect quality. One trade-off is that information of reasonable quality is not accepted.

We should reconsider this policy. At least non-vendor (or not-the-vendor) CNAs should be permitted to submit affected product information.

ADP containers in JSON 5 may provide a technical solution.

@zmanion zmanion added this to CVE Oct 5, 2024
@zmanion zmanion moved this to Slow progress in CVE Oct 5, 2024
@zmanion zmanion moved this from Slow progress to Backlog in CVE Nov 28, 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

1 participant