-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Cherry pick][RHOAIENG-15961] Fix Starlette Denial of service (DoS) via multipart/form-data (#4006) #735
Conversation
…#4006) chore: Fix CVE-2024-47874 Signed-off-by: Spolti <[email protected]>
@hdefazio can you please open a jira for this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also you might need to run poetry lock --no-update
to fix the storage-initializer build, it can be verified locally by building the container.
Yes - there is already a JIRA for this: RHOAIENG-14604 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hdefazio, spolti The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
353ced9
into
red-hat-data-services:rhoai-2.16
Isn't this one:? https://issues.redhat.com/browse/RHOAIENG-15961 |
Oops yes - I copied the wrong link |
chore: Fix CVE-2024-47874
Cherry-picks kserve#4006
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Type of changes
Please delete options that are not relevant.
Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.
Test A
Test B
Logs
Special notes for your reviewer:
Checklist:
Release note:
Re-running failed tests
/rerun-all
- rerun all failed workflows./rerun-workflow <workflow name>
- rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.