[GHSA-rpw6-9xfx-jvcx] Directory Traversal in Archive_Tar - #9303
Closed
nikpivkin wants to merge 1 commit into
Closed
Conversation
github-actions
Bot
changed the base branch from
main
to
nikpivkin/advisory-improvement-9303
September 1, 2026 15:42
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The advisory prose contradicts the corrected range, and the CVSS edit unnecessarily removes valid metadata.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Corrects Archive_Tar advisory metadata so OSV marks version 1.4.12 as patched.
Changes:
- Updates the fixed version from 1.4.13 to 1.4.12.
- Modifies the CVSS vector and timestamp.
File summaries
| File | Description |
|---|---|
GHSA-rpw6-9xfx-jvcx.json |
Updates affected-version and severity metadata. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 2
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| { | ||
| "type": "CVSS_V3", | ||
| "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N/E:H" | ||
| "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N" |
| }, | ||
| { | ||
| "fixed": "1.4.13" | ||
| "fixed": "1.4.12" |
nikpivkin
marked this pull request as draft
September 1, 2026 16:47
Author
|
Closing this. I missed the note in the advisory details, which says that 1.4.13 was chosen on purpose because the fix in 1.4.12 introduced a bug, so 1.4.13 is the earliest working version. |
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
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 affected entry has the version range
<= 1.4.11and1.4.13as the first patched version. The fix shipped in 1.4.12, so the first patched version should be1.4.12. The range is already correct.Evidence: the fix for CVE-2020-28948 is pear/Archive_Tar@cde4605. Tag 1.4.11 does not contain it and tag 1.4.12 does. In pear/Archive_Tar#38 a maintainer confirms that 1.4.13 was not a security release, the changes in it fixed a regression caused by the fix itself.
Because the range and the first patched version disagree, the OSV export puts
1.4.13into thefixedevent and keeps the range indatabase_specific.last_known_affected_version_range. That marks 1.4.12 as affected, although the fix is in it.The CVSS vector lost its
/E:Hpart because the form refused to submit with "The entered vector string contains an error and cannot populate a score". The score is unchanged at 7.5.