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

feat: improve handling when some CPEs have 0 CVEs associated? #3909

Open
terriko opened this issue Mar 8, 2024 · 1 comment
Open

feat: improve handling when some CPEs have 0 CVEs associated? #3909

terriko opened this issue Mar 8, 2024 · 1 comment

Comments

@terriko
Copy link
Contributor

terriko commented Mar 8, 2024

For instance, in dumping the CVEData when there's no CVEs, I came across this occasion where there's two other instances of dnsmasq for vendors dnsmasq and the_kelleys. The instance of dnsmasq with vendor name thekelleys (no underscore) actually has 13 CVEs with all the correct data.

=== ProductInfo(vendor='dnsmasq', product='dnsmasq', version='2.78') CVEData(None, {'cves': []})
=== ProductInfo(vendor='the_kelleys', product='dnsmasq', version='2.78') CVEData(None, {'cves': []})

Originally posted by @wideglide in #3899 (comment)

As I mentioned in the bug, we are working on a few things to avoid this kind of result, but while we're working on those slower improvements we may also want to do something fancy display-wise for cases where one or more of the CPEs (e.g. {vendor, product}) don't have any CVEs associated with them. Maybe just don't display them if they're not useful? Maybe put them in as a footnote? Not sure the best solution here but it seems like we could probably do better, anyhow.

@joydeep049
Copy link
Contributor

joydeep049 commented Mar 9, 2024

Can I work on this?
Also, Can you look at this and this. I think one is ready to merge and the other needs more a bit more discussion

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