fix: pax-logging-log4j2 ranges affected by CVE-2021-45046
#5521
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
This PR fixes the ranges of `pax-logging-log4j2` affected by CVE-2021-45046. In my previous PRs for CVE-2021-45046 (github#5502) 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 |
There was a problem hiding this comment.
Pull Request Overview
This PR updates the version ranges for the Maven package "org.ops4j.pax.logging:pax-logging-log4j2" to precisely reflect which 1.x and 2.x releases are affected by CVE‑2021‑45046.
- Added a range for versions introduced in 1.10.0 with a fix in 1.10.8
- Added a range for versions introduced in 1.11.0 with a fix in 1.11.11
- Added a range for versions introduced in 2.0.0 with a fix in 2.0.12
Comments suppressed due to low confidence (1)
advisories/github-reviewed/2021/12/GHSA-7rjr-3q55-vv33/GHSA-7rjr-3q55-vv33.json:68
- [nitpick] Consider adding an inline comment to clarify the rationale for splitting the version ranges to reflect the distinct security fixes, referencing the detailed release table in the PR description.
{ "fixed": "1.9.2" }
71f61d2
into
github:ppkarwasz/advisory-improvement-5521
2 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! |
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.
This PR fixes the ranges of
pax-logging-log4j2affected by CVE-2021-45046.In my previous PRs for CVE-2021-45046 (#5502) all versions 1.x of
pax-logging-log4j2were listed as affected. As it turns out, this is incorrect, since 7 security releases of version 1.x were created after December 2021, as summarized by the table below: