Repository navigation
Conversation
findIntroducedVersion picked the first CPE match with a versionStartIncluding, regardless of which vulnerable branch it described. When a CVE was fixed independently on multiple branches (e.g. perl CVE-2018-18311, fixed at 5.26.3 and separately at 5.28.1), this could pair an introduced version from one branch with the Alpine secfix from a different, unrelated branch, producing an inverted and unsatisfiable range (introduced > fixed). Scanners then treated every higher version as affected, causing false positives long after the real fix. Only use a candidate introduced version when it sorts before the Alpine fixed version, picking the closest qualifying one and falling back to "0" otherwise.
Collaborator
|
Please read our contributing guide before opening pull requests |
This branch has not been deployed
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.
findIntroducedVersion picked the first CPE match with a versionStartIncluding, regardless of which vulnerable branch it described. When a CVE was fixed independently on multiple branches (e.g. perl CVE-2018-18311, fixed at 5.26.3 and separately at 5.28.1), this could pair an introduced version from one branch with the Alpine secfix from a different, unrelated branch, producing an inverted and unsatisfiable range (introduced > fixed). Scanners then treated every higher version as affected, causing false positives long after the real fix.
Only use a candidate introduced version when it sorts before the Alpine fixed version, picking the closest qualifying one and falling back to "0" otherwise.
Fixes #5634