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 fixes #684

Open
vivekkumarchaurasia123 opened this issue Nov 18, 2024 · 1 comment
Open

CVE fixes #684

vivekkumarchaurasia123 opened this issue Nov 18, 2024 · 1 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.

Comments

@vivekkumarchaurasia123
Copy link

vivekkumarchaurasia123 commented Nov 18, 2024

What happened?:
Can anyone please upgrade Prometheus adapter to fix following CVE's

CVE-2013-4235 | MEDIUM
CVE-2016-20013 | HIGH
CVE-2016-2781 | MEDIUM
CVE-2017-11164 | HIGH
CVE-2022-3219 | LOW
CVE-2022-41409 | HIGH
CVE-2023-26604 | HIGH
CVE-2023-29383 | LOW
CVE-2023-45918 | MEDIUM
CVE-2023-50495 | MEDIUM
CVE-2023-7008 | MEDIUM
CVE-2024-2236 | MEDIUM
CVE-2024-34155 | MEDIUM
CVE-2024-34156 | HIGH
CVE-2024-34158 | HIGH

What did you expect to happen?:
Fix the CVE

Please provide the prometheus-adapter config:
NA

Please provide the HPA resource used for autoscaling:
NA

Please provide the HPA status:

Please provide the prometheus-adapter logs with -v=6 around the time the issue happened:
NA

Anything else we need to know?:

Environment:

  • prometheus-adapter version:
  • prometheus version:
  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • Other info:
@vivekkumarchaurasia123 vivekkumarchaurasia123 added the kind/bug Categorizes issue or PR as related to a bug. label Nov 18, 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 Nov 18, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If prometheus-adapter 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-sigs/prow repository.

@vivekkumarchaurasia123 vivekkumarchaurasia123 changed the title CVE fixes for version v0.12.0 CVE fixes Nov 29, 2024
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

2 participants