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

Optional External Data Source Reference for Maven Packages #711

Closed
spiffcs opened this issue Apr 7, 2022 · 0 comments · Fixed by #714
Closed

Optional External Data Source Reference for Maven Packages #711

spiffcs opened this issue Apr 7, 2022 · 0 comments · Fixed by #714
Assignees
Labels
enhancement New feature or request

Comments

@spiffcs
Copy link
Contributor

spiffcs commented Apr 7, 2022

What would you like to be added:
With the addition of anchore/syft#887 syft now is able to provide sha1 digests for java packages.

Grype should optionally (off by default) be able to use this data to query upstream java repository sources to enhance the fidelity of matching against vulnerability data that is based on Maven or other registry information.

Why is this needed:
Grype currently has a gap where, when trying to match off package name, it misses positive results for vulnerabilities stored by their upstream registry information (GHSA, MAVEN) rather than MANIFEST.MF naming conventions discovered at the time of SBOM generation.

Additional context:
See #704 for more context on this kind of miss-on-detection.

@spiffcs spiffcs added the enhancement New feature or request label Apr 7, 2022
@spiffcs spiffcs self-assigned this Apr 7, 2022
@spiffcs spiffcs linked a pull request Apr 11, 2022 that will close this issue
1 task
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

Successfully merging a pull request may close this issue.

1 participant