-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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-2024-6119 in controller:v1.11.2 #11965
Labels
kind/bug
Categorizes issue or PR as related to a bug.
needs-priority
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
k8s-ci-robot
added
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
needs-priority
labels
Sep 10, 2024
It will be fixed in the next release of the controller /triage-accepted |
|
/triage accepted |
k8s-ci-robot
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Sep 11, 2024
@longwuyuan Do you have any estimated date on the next release of the controller? |
We are currently working on it. There will be a v1.12.0 (maybe a beta first), v1.11.3 and v1.10.5, all of them containing the required patches. |
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-priority
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What scanner and version reported the CVE?
What CVE was reported in the scanner findings?
What versions of the controller did you test with?
registry.k8s.io/ingress-nginx/controller:v1.11.2@sha256:d5f8217feeac4887cb1ed21f27c2674e58be06bd8f5184cacea2a69abaf78dce
Please provider other details that will help us determine the severity of the issue
CVE-2024-6119
Our internal scanner labeled it as severity High.
The text was updated successfully, but these errors were encountered: