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

Suppressed CVEs shown even without --show-suppressed #1278

Closed
mgzenitech opened this issue May 8, 2023 · 2 comments · Fixed by #1322
Closed

Suppressed CVEs shown even without --show-suppressed #1278

mgzenitech opened this issue May 8, 2023 · 2 comments · Fixed by #1322
Labels
bug Something isn't working

Comments

@mgzenitech
Copy link

What happened:

.grype.yaml

---
ignore:
  vulnerability: CVE-2018-20225
...

When running grype ${docker_image} -f negligible I get suppressed items in the list.

NAME  INSTALLED  FIXED-IN  TYPE    VULNERABILITY   SEVERITY          
pip   23.1.2               python  CVE-2018-20225  High (suppressed) 

What you expected to happen:

Message is output that shows no CVEs detected.

How to reproduce it (as minimally and precisely as possible):

Run any Python image with pip preinstalled image from Docker hub.

Anything else we need to know?:

Environment:

  • Output of grype version:
Application:          grype
Version:              0.61.1
Syft Version:         v0.79.0
BuildDate:            2023-04-21T17:11:07Z
GitCommit:            3caabc87114a3e0cbfbac7770989bc81e2f5a957
GitDescription:       v0.61.1
Platform:             linux/amd64
GoVersion:            go1.19.8
Compiler:             gc
Supported DB Schema:  5
  • OS (e.g: cat /etc/os-release or similar):
@mgzenitech mgzenitech added the bug Something isn't working label May 8, 2023
@tgerla
Copy link
Contributor

tgerla commented May 18, 2023

Hi @mgzenitech, I've been able to reproduce this using:

grype -o table python

...with the appropriate CVE set to be ignored in my configuration file. I think there is probably a bug in the --show-suppressed logic. We will add this to our backlog for further investigation and hopefully a fix. Thanks for the report!

@tgerla
Copy link
Contributor

tgerla commented May 18, 2023

Related to: #1053

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants