Update rack version from 2.2.6.2 -> 2.2.6.4 because of possible DOS Vulnerability in Multipart MIME parsing chef-server-ctl #3733
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
👷 Deploy Preview for chef-server processing.
|
|
The AdHoc Pipeline for this one is green. |
talktovikas
force-pushed
the
CHEF-6747
branch
from
a34d2db to
4e152f9
Compare
jashaik
approved these changes
Nov 21, 2023
|
@talktovikas Please add the issue description with reason for this update. |
Signed-off-by: talktovikas <[email protected]>
|
Kudos, SonarCloud Quality Gate passed!
|
|
The Umbrella pipeline for this change: https://buildkite.com/chef/chef-umbrella-main-chef-server/builds/2247. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Since the last version had "Rack" had this vulnerability of DOS in Multipart parsing in chef-server-ctl upgrading it to the latest version would fix this issue.
This Issue was primarily seen with the dependabot alert which also suggested the fix to it.
Here are the link:
Issues Resolved
Now, Upgrading Rack fixes our vulnerability.
[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant]
Check List