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

Provide information on incomplete vulnerability matching for project #2865

Open
2 tasks done
savek-cc opened this issue Jul 3, 2023 · 0 comments
Open
2 tasks done
Labels
enhancement New feature or request

Comments

@savek-cc
Copy link

savek-cc commented Jul 3, 2023

Current Behavior

DependencyTrack is configured to use multiple sources for vulnerability information; one of which is OSSI.
If access to OSSI fails for whatever reason (e.g. rate limit - but also like #2857), no sonatype-* vulnerabilities are reported for that project.
In this case, you can have to projects with identical components - but a complete different list of vulnerabilities.
Apparently there is no way for a user to detect if vulnerability matching was complete/successful for all sources.

Proposed Behavior

Add a status field to the project properties where it is visible whether errors were encountered during vulnerability matching.
This allows the user to actually trust the list of vulnerabilities - and know where they might be incomplete.

Checklist

@savek-cc savek-cc added the enhancement New feature or request label Jul 3, 2023
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

1 participant