Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libarchive/3.7.8 package update #47521

Merged
merged 2 commits into from
Mar 21, 2025

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Mar 20, 2025

Signed-off-by: wolfi-bot <121097084+wolfi-bot@users.noreply.github.com>
@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. labels Mar 20, 2025
Copy link
Contributor Author

octo-sts bot commented Mar 20, 2025

⚠️ EXPERIMENTAL

Please use 👍 or 👎 on this comment to indicate if you agree or disagree with the recommendation.

To provide more detailed feedback please comment on the recommendation prefixed with /ai-verify:

e.g. /ai-verify partially helpful but I also added bash to the build environment

Gen AI suggestions to solve the build error:

Let me analyze the error and provide a solution:

• Detected Error:

Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
Hunk #1 ignored at 1146.

• Error Category: Build/Patch

• Failure Point: The patch step is failing because the patch appears to be already applied or in reverse format

• Root Cause Analysis:
The patch system is detecting that the CVE patch being applied either has:

  1. Already been applied to the source code
  2. Is in reverse format
  3. The patch context doesn't match the source file

• Suggested Fix:

  1. Remove the existing patches from the patch section since they appear to be included in version 3.7.8:
  - uses: patch
    with:
      patches: CVE-2024-57970.patch CVE-2025-1632_CVE-2025-25724.patch

• Explanation:
Based on the patch date (Dec 9, 2024) and the version being built (3.7.8), it appears these CVE fixes are already included in the upstream release. Version 3.7.8 likely already contains these security fixes, making the patches unnecessary and causing conflicts.

• Additional Notes:

  • Always check if newer versions include security fixes before applying patches
  • The version number and patch dates suggest these fixes are already incorporated
  • If these CVEs still need to be addressed, verify against the official security advisories that they're not already fixed in 3.7.8

• References:

@octo-sts octo-sts bot added the ai/skip-comment Stop AI from commenting on PR label Mar 20, 2025
@amberarcadia amberarcadia self-assigned this Mar 20, 2025
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Mar 21, 2025
@amberarcadia amberarcadia requested a review from a team March 21, 2025 20:11
@OddBloke OddBloke merged commit abc18a6 into main Mar 21, 2025
21 checks passed
@OddBloke OddBloke deleted the wolfictl-f4b03ce2-00fc-4f43-a71b-7abc2f0898c9 branch March 21, 2025 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ai/skip-comment Stop AI from commenting on PR automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. request-version-update request for a newer version of a package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants