[GHSA-jfh8-c2jp-5v3q] Remote code injection in Log4j #2445
Closed
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
github-actions
bot
changed the base branch from
main
to
jensdietrich/advisory-improvement-2445
|
@darakian This PR has been stuck for some time now, same issue here: #2444. Is there anything we can do to help? We have a number of similar PRs in the pipeline, we expect to find clones for most of the artifacts associated with the CVEs listed in https://github.com/jensdietrich/xshady/ (29 CVEs atm, 6 already reported as PRs, 4 PRs accepted, 2 open including this one), we are running the analyses atm. Please let us know what the best way is to go about this. |
|
Hey @jensdietrich, sorry about the delay. We've been swamped on our end. I'll try to get to this and the other PR this week 🙇 |
|
Manually merged in |
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.
Updates
Comments
Several other components are also affected as a result of cloning or shading. Proof-of-Vulnerability projects with tests to verify the presence of the CVE can be found here: https://github.com/jensdietrich/xshady-release/ , the process was the same used for #2258 .