fix: add data for pax-logging-log4j2 version 1.x
#5519
Closed
+136
−4
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` 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 |
There was a problem hiding this comment.
Pull Request Overview
This PR updates the advisory JSON files for pax-logging-log4j2 1.x to correct the ranges affected by four CVEs in log4j-core by adding new fixed version events.
- Updated fixed version events for version 1.9.2 across all advisories
- Introduced version-specific fixed events for 1.10.x and 1.11.x based on different CVE fixes
- Retained existing version 2.0.x fixed events without changes
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| advisories/github-reviewed/2022/01/GHSA-8489-44mv-ggj8/GHSA-8489-44mv-ggj8.json | Added fixed events for 1.9.2, 1.10.9, and 1.11.13 |
| advisories/github-reviewed/2021/12/GHSA-p6xc-xr62-6r2g/GHSA-p6xc-xr62-6r2g.json | Added fixed events for 1.9.2, 1.10.9, and 1.11.12 |
| advisories/github-reviewed/2021/12/GHSA-jfh8-c2jp-5v3q/GHSA-jfh8-c2jp-5v3q.json | Added fixed events for 1.9.2, 1.10.8, and 1.11.10 |
| advisories/github-reviewed/2021/12/GHSA-7rjr-3q55-vv33/GHSA-7rjr-3q55-vv33.json | Added fixed events for 1.9.2, 1.10.8, and 1.11.11 |
|
As suggested by the "Processing advisory improvement" check, this PR was split into: |
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-log4j2releases affected by four CVEs inlog4j-core.In my previous PRs for CVE-2021-44228 (#5501), CVE-2021-45046 (#5502), CVE-2021-45105 (#5503), and CVE-44832 (#5504), 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: