Repository navigation
fix(security): identify exact vendor-patched curl packages in VEX - #301
Merged
Merged
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
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.
The final-artifact scan correctly blocked the previous unpublished 533 candidate. All three installed curl packages are now the official Ubuntu 8.18.0-1ubuntu2.8 security update, but the scanner feed still reports 18 curl CVEs without a fixed version. The signed Ubuntu package changelog explicitly lists all 18 fixes; Ubuntu USN-8927-1 identifies the three fixed packages and each curl upstream advisory identifies its fix commit. Add only 18 fixed OpenVEX records for the exact three 8.18.0-1ubuntu2.8 amd64 package PURLs, with exact official deb hashes and source evidence. Preserve all 51 existing decisions, the 20 genuinely unfixed Medium findings and the HIGH/CRITICAL release block. The production VEX predicate now locks the exact added set; focused mutation tests reject old versions, missing packages, wildcards, unknown CVEs, unsupported status and missing evidence. No HIGH exception, vendor-pending expansion, runtime patch or unrelated test replay. Require all normal source/CodeQL checks and the original final-artifact publication scan.