fix: pax-logging-log4j2 ranges affected by CVE-2021-45105
#5522
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-45105. In my previous PRs for CVE-2021-45105 (github#5503) 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 corrects the version ranges for the vulnerability in the "pax-logging-log4j2" package affected by CVE-2021-45105. It updates the JSON advisory file to reflect accurate fixed versions for both 1.x and 2.x releases.
- Added a version range block for the 1.10.x series (introduced "1.10.0" and fixed "1.10.9").
- Added a version range block for the 1.11.x series (introduced "1.11.0" and fixed "1.11.12").
- Added a version range block for the 2.0.x series (introduced "2.0.0" and fixed "2.0.13").
advisories/github-reviewed/2021/12/GHSA-p6xc-xr62-6r2g/GHSA-p6xc-xr62-6r2g.json
Show resolved
Hide resolved
There was a problem hiding this comment.
Pull Request Overview
This PR updates the vulnerability advisory ranges for pax-logging-log4j2 to correctly reflect the versions fixed for CVE-2021-45105.
- Adds a "fixed": "1.9.2" event to the pre-existing range.
- Introduces new range blocks for versions 1.10.0–1.10.9 and 1.11.0–1.11.12.
- Adds a range block intended for later versions with a fixed version of 2.0.13.
Comments suppressed due to low confidence (1)
advisories/github-reviewed/2021/12/GHSA-p6xc-xr62-6r2g/GHSA-p6xc-xr62-6r2g.json:123
- The range block with a fixed version of "2.0.13" appears to have an incorrect introduced version; it should likely use "introduced": "2.0.0" to accurately represent the 2.x series.
"introduced": "1.11.0"
a2286e9
into
github:ppkarwasz/advisory-improvement-5522
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-45105.In my previous PRs for CVE-2021-45105 (#5503) 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 to address those issues, as summarized by the table below: