[GHSA-fjqv-vj6q-4fcm] A flaw was found in libarchive. A NULL pointer...#7434
Open
kientzle wants to merge 1 commit intokientzle/advisory-improvement-7434from
Open
[GHSA-fjqv-vj6q-4fcm] A flaw was found in libarchive. A NULL pointer...#7434kientzle wants to merge 1 commit intokientzle/advisory-improvement-7434from
kientzle wants to merge 1 commit intokientzle/advisory-improvement-7434from
Conversation
github-actions
bot
changed the base branch from
main
to
kientzle/advisory-improvement-7434
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
1 participant
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 libarchive team has investigated this report at:
libarchive/libarchive#2904
And we believe this should be rejected.
We agree with the reporter that under certain circumstances, a NULL pointer will be incremented by libarchive. This is technically Undefined Behavior according to the C standard, but it has no effect in this case, since under these conditions the incremented pointer is never dereferenced. We do plan to fix the code to avoid this UB, but do not feel it merits a CVE.
(This does not impact any Github product, so I choose "Composer" since I was forced to choose something.)