Lock to rack-cors 2.0.0 to avoid problem with rack-cors 2.0.1#10173
Merged
Lock to rack-cors 2.0.0 to avoid problem with rack-cors 2.0.1#10173
rack-cors 2.0.0 to avoid problem with rack-cors 2.0.1#10173Conversation
rack-cors 2.0.1 by Locking Version to rack-cors 2.0.0`
rack-cors 2.0.1 by Locking Version to rack-cors 2.0.0`rack-cors 2.0.1 by Locking Version to rack-cors 2.0.0
rack-cors 2.0.1 by Locking Version to rack-cors 2.0.0rack-cors 2.0.0 to avoid problem with rack-cors 2.0.1
… avoid vulnerability in version 2.0.1
mitchellhenke
approved these changes
Feb 28, 2024
jmax-gsa
pushed a commit
that referenced
this pull request
Feb 28, 2024
…0173) * Mitigate permissions concern in rack-cors by locking version * changelog: Internal, Dependencies, Lock rack-cors to version 2.0.0 to avoid vulnerability in version 2.0.1
This file contains hidden or 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
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.
🛠 Summary of changes
Right now all lint tasks are failing in
mainbecause there's a newly reported file permission vulnerability inrack-cors(link) version 2.0.1 (latest). This PR addresses that by locking our version to 2.0.0, the latest version ofrack-corswithout this vulnerability (link).Presumably we'll be able to use 2.0.1 again once they've patched the problem.
The error:
📜 Testing Plan
make lintinmainnotice the failure.make lintin this branch, the failure is gone.