[GHSA-jfh8-c2jp-5v3q] Remote code injection in Log4j #5501
Merged
Conversation
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
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
Files not reviewed (1)
- advisories/github-reviewed/2021/12/GHSA-jfh8-c2jp-5v3q/GHSA-jfh8-c2jp-5v3q.json: Language not supported
ddc0490
into
ppkarwasz/advisory-improvement-5501
4 checks passed
|
Hi @ppkarwasz! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future! |
ppkarwasz
added a commit
to ppkarwasz/advisory-database
that referenced
this pull request
May 9, 2025
This PR fixes the ranges of `pax-logging-log4j2` releases affected by four CVEs in `log4j-core`. In my previous PRs for CVE-2021-44228 (github#5501), CVE-2021-45046 (github#5502), CVE-2021-45105 (github#5503), and CVE-44832 (github#5504), all versions 1.x of `pax-logging-log4j2` were listed as affected. As it turns out, this is incorrect, since 7 security releases of version 1.x were created to address those issues, as summarized by the table below: | PAX Logging version | Log4j Core version | Fixed CVEs | |---------------------|--------------------|--------------------------------| | 1.9.2 | 2.12.4 | all 4 CVEs | | 1.10.8 | 2.12.2 | CVE-2021-44228, CVE-2021-45046 | | 1.10.9 | 2.12.4 | CVE-2021-45105, CVE-2021-44832 | | 1.11.10 | 2.15.0 | CVE-2021-44228 | | 1.11.11 | 2.16.0 | CVE-2021-45046 | | 1.11.12 | 2.17.0 | CVE-2021-45105 | | 1.11.13 | 2.17.1 | CVE-2021-44832 |
ppkarwasz
added a commit
to ppkarwasz/advisory-database
that referenced
this pull request
May 9, 2025
This PR fixes the ranges of `pax-logging-log4j2` releases affected by CVE-2021-44228 In my previous PRs for CVE-2021-44228 (github#5501), all versions 1.x of `pax-logging-log4j2` were listed as affected. As it turns out, this is incorrect, since 7 security releases of version 1.x were created to address those issues, as summarized by the table below: | PAX Logging version | Log4j Core version | Fixed CVEs | |---------------------|--------------------|--------------------------------| | 1.9.2 | 2.12.4 | all 4 CVEs | | 1.10.8 | 2.12.2 | CVE-2021-44228, CVE-2021-45046 | | 1.10.9 | 2.12.4 | CVE-2021-45105, CVE-2021-44832 | | 1.11.10 | 2.15.0 | CVE-2021-44228 | | 1.11.11 | 2.16.0 | CVE-2021-45046 | | 1.11.12 | 2.17.0 | CVE-2021-45105 | | 1.11.13 | 2.17.1 | CVE-2021-44832 |
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
The
pax-logging-log4j2artifact shadeslog4j-corewith minimal modifications.The correspondence between
pax-logging-log4j2versions and the embeddedlog4j-coreversion is given by the table below:pax-logging-log4j2versionlog4j-coreversion