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

CVE in v2.11.0 Image #2349

Closed
nikhil-bhat opened this issue Mar 25, 2024 · 8 comments
Closed

CVE in v2.11.0 Image #2349

nikhil-bhat opened this issue Mar 25, 2024 · 8 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@nikhil-bhat
Copy link

Ran image Scan docker scout cves registry.k8s.io/kube-state-metrics/kube-state-metrics:v2.11.0 and found CVE:

Packages and Vulnerabilities

https://scout.docker.com/v/CVE-2024-24786
GHSA-8r3f-844c-mc37

image

CVE report should be clean:

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

 docker scout cves registry.k8s.io/kube-state-metrics/kube-state-metrics:v2.11.0

Anything else we need to know?:
I see 3 open PRs #2342 #2341 #2340 which reference this issue.
I see based on GHSA-8r3f-844c-mc37 that issue is related to protobuf, ran a go mod why to check from which dependency these indirect dependency are arising. It seems it is due to prometheus

image

I am willing to contribute to fix the issue in case the og contributors need any help

Environment:

  • kube-state-metrics version: 2.11.0
  • Kubernetes version (use kubectl version): NA
  • Cloud provider or hardware configuration: NA
  • Other info: NA
@nikhil-bhat nikhil-bhat added the kind/bug Categorizes issue or PR as related to a bug. label Mar 25, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 25, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@nikhil-bhat nikhil-bhat changed the title CVE in v2.11,0 Image CVE in v2.11.0 Image Mar 25, 2024
@CatherineF-dev
Copy link
Contributor

Could you run with main branch again?

#2352 was merged recently.

@nikhil-bhat
Copy link
Author

@CatherineF-dev i built the image locally . that image seems to be clear of any vulnerability. However is the main branch image published anywhere. Do you know when v2.12.0 will be released.
image

@CatherineF-dev
Copy link
Contributor

Could you verify v2.12.0? Seems released #2335

@nikhil-bhat
Copy link
Author

hi @CatherineF-dev i see #2335 is merged but it is not released yet it seems.

@CatherineF-dev
Copy link
Contributor

@CatherineF-dev
Copy link
Contributor

Could you try again

@nikhil-bhat
Copy link
Author

Thanks a ton @CatherineF-dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants