-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Bump sirupsen/logrus from 1.9.0 to 1.9.3 to fix vulnerability PRISMA-2023-0056 #21932
Open
tian-ma
wants to merge
7
commits into
hashicorp:main
Choose a base branch
from
tian-ma:fix_logrus_CVE
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+3
−3
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
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
github-actions
bot
added
the
pr/dependencies
PR specifically updates dependencies of project
label
Nov 7, 2024
tian-ma
changed the title
upgrade sirupsen/logrus to 1.9.3 to fix CVE: PRISMA-2023-0056
upgrade sirupsen/logrus to 1.9.3 to fix vulnerability PRISMA-2023-0056
Nov 7, 2024
tian-ma
changed the title
upgrade sirupsen/logrus to 1.9.3 to fix vulnerability PRISMA-2023-0056
bump sirupsen/logrus to 1.9.3 to fix vulnerability PRISMA-2023-0056
Nov 8, 2024
tian-ma
changed the title
bump sirupsen/logrus to 1.9.3 to fix vulnerability PRISMA-2023-0056
Bump sirupsen/logrus from 1.9.0 to 1.9.3 to fix vulnerability PRISMA-2023-0056
Nov 8, 2024
NiniOak
approved these changes
Nov 27, 2024
who can look at this PR? |
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
Twistlock scan reports PRISMA-2023-0056
caused by sirupsen/logrus as described here sirupsen/logrus#1370
The fix is upgrade of logrus to 1.9.3
https://github.com/sirupsen/logrus/releases/tag/v1.9.3
This fixes issue #20605
Testing & Reproduction steps
Links
PR Checklist