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

Should vuln db lastUpdate be optional in vulns predicate #409

Open
lumjjb opened this issue Nov 16, 2024 · 0 comments
Open

Should vuln db lastUpdate be optional in vulns predicate #409

lumjjb opened this issue Nov 16, 2024 · 0 comments

Comments

@lumjjb
Copy link

lumjjb commented Nov 16, 2024

As part of vulns 0.2 predicate, there is a vuln db lastUpdate field which is required. This may not necessary be present with some scanners. Some vuln databases only expose the lastUpdate for an entry for a vulnerability and not the version of the entire database (e.g. in OSV), as well as MITRE (to my knowledge).

Thus, i'm wondering if the lastUpdate information should be optional. Following up as discussions from this thread: #392 (comment)

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