[GH-ISSUE #822] [BUG] Vulnerability scan is not working #517

New issue

Closed

opened 2026-02-25 20:35:56 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 20:35:56 +03:00

Owner

Originally created by @ngosang on GitHub (Jul 28, 2022).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/822

The GitHub actions are successful.. => https://github.com/benbusby/whoogle-search/actions

But, if I run grype in my server I see that:

Docker image: benbusby/whoogle-search:0.7.4
curl                   7.80.0-r1         7.80.0-r2         apk   CVE-2022-27782  High      
curl                   7.80.0-r1         7.80.0-r2         apk   CVE-2022-27781  High      
curl                   7.80.0-r1         7.80.0-r2         apk   CVE-2022-32207  Critical  
curl                   7.80.0-r1         7.80.0-r2         apk   CVE-2022-27780  High      
libcrypto1.1           1.1.1o-r0         1.1.1q-r0         apk   CVE-2022-2097   High      
libcurl                7.80.0-r1         7.80.0-r2         apk   CVE-2022-27781  High      
libcurl                7.80.0-r1         7.80.0-r2         apk   CVE-2022-27782  High      
libcurl                7.80.0-r1         7.80.0-r2         apk   CVE-2022-27780  High      
libcurl                7.80.0-r1         7.80.0-r2         apk   CVE-2022-32207  Critical  
libssl1.1              1.1.1o-r0         1.1.1q-r0         apk   CVE-2022-2097   High      
ncurses-libs           6.3_p20211120-r0  6.3_p20211120-r1  apk   CVE-2022-29458  High      
ncurses-terminfo-base  6.3_p20211120-r0  6.3_p20211120-r1  apk   CVE-2022-29458  High

Originally created by @ngosang on GitHub (Jul 28, 2022). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/822 The GitHub actions are successful.. => https://github.com/benbusby/whoogle-search/actions But, if I run grype in my server I see that: ``` Docker image: benbusby/whoogle-search:0.7.4 curl 7.80.0-r1 7.80.0-r2 apk CVE-2022-27782 High curl 7.80.0-r1 7.80.0-r2 apk CVE-2022-27781 High curl 7.80.0-r1 7.80.0-r2 apk CVE-2022-32207 Critical curl 7.80.0-r1 7.80.0-r2 apk CVE-2022-27780 High libcrypto1.1 1.1.1o-r0 1.1.1q-r0 apk CVE-2022-2097 High libcurl 7.80.0-r1 7.80.0-r2 apk CVE-2022-27781 High libcurl 7.80.0-r1 7.80.0-r2 apk CVE-2022-27782 High libcurl 7.80.0-r1 7.80.0-r2 apk CVE-2022-27780 High libcurl 7.80.0-r1 7.80.0-r2 apk CVE-2022-32207 Critical libssl1.1 1.1.1o-r0 1.1.1q-r0 apk CVE-2022-2097 High ncurses-libs 6.3_p20211120-r0 6.3_p20211120-r1 apk CVE-2022-29458 High ncurses-terminfo-base 6.3_p20211120-r0 6.3_p20211120-r1 apk CVE-2022-29458 High ```

kerem

2026-02-25 20:35:56 +03:00

closed this issue
added the
bug

Stale
labels

kerem commented

2026-02-25 20:35:56 +03:00

Author

Owner

@benbusby commented on GitHub (Aug 1, 2022):

Are you running that with --only-fixed?

@benbusby commented on GitHub (Aug 1, 2022): Are you running that with `--only-fixed`?

kerem commented

2026-02-25 20:35:56 +03:00

Author

Owner

@ngosang commented on GitHub (Aug 1, 2022):

Yes

@ngosang commented on GitHub (Aug 1, 2022): Yes

kerem commented

2026-02-25 20:35:56 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 15, 2025):

This issue has been automatically marked as stale due to inactivity. If it is still valid please comment within 7 days or it will be auto-closed.

@github-actions[bot] commented on GitHub (Sep 15, 2025): This issue has been automatically marked as stale due to inactivity. If it is still valid please comment within 7 days or it will be auto-closed.

kerem commented

2026-02-25 20:35:56 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 23, 2025):

Closing this issue due to prolonged inactivity.

@github-actions[bot] commented on GitHub (Sep 23, 2025): Closing this issue due to prolonged inactivity.

kerem referenced this issue

2026-02-25 20:37:03 +03:00

[PR #517] [MERGED] Add Update Available warning #901