upgrade log4j to 2.17 #7616
Merged
upgrade log4j to 2.17 #7616
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
|
@lbergelson I cannot update #7611 with these changes until the Docker image(s) are regenerated, as WDL workflows (in this context) point to a Docker image. Since an image with these changes isn't currently on DockerHub, those workflows remain insecure. I would like to propose tagging a new release (4.2.4.1) that contains #7616 and pushing those as tag 4.2.4.1 onto DockerHub. Once that is done, I can update the workflows accordingly. context: #7617 (comment) |
|
@aofarrel Yes, I'm going to do that very soon. |
This was referenced Mar 17, 2023
Closed
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.
No description provided.