Skip to content

Conversation

@red-hat-konflux
Copy link
Contributor

This PR contains the following updates:

File rpms.in.yaml:

Package Change
coreutils 8.30-15.el8 -> 8.30-16.el8_10
coreutils-common 8.30-15.el8 -> 8.30-16.el8_10
curl 7.61.1-34.el8_10.8 -> 7.61.1-34.el8_10.9
dracut 049-237.git20250603.el8_10 -> 049-239.git20251127.el8_10
findutils 1:4.6.0-23.el8_10 -> 1:4.6.0-24.el8_10
libblkid 2.32.1-46.el8 -> 2.32.1-47.el8_10
libcurl 7.61.1-34.el8_10.8 -> 7.61.1-34.el8_10.9
libfdisk 2.32.1-46.el8 -> 2.32.1-47.el8_10
libmount 2.32.1-46.el8 -> 2.32.1-47.el8_10
libsmartcols 2.32.1-46.el8 -> 2.32.1-47.el8_10
libuuid 2.32.1-46.el8 -> 2.32.1-47.el8_10
pam 1.3.1-38.el8_10 -> 1.3.1-39.el8_10
shadow-utils 2:4.6-22.el8 -> 2:4.6-23.el8_10
tzdata 2025b-1.el8 -> 2025c-1.el8
util-linux 2.32.1-46.el8 -> 2.32.1-47.el8_10

curl: libcurl: Curl out of bounds read for cookie path

CVE-2025-9086

More information

Details

  1. A cookie is set using the secure keyword for https://target
  2. curl is redirected to or otherwise made to speak with http://target (same
    hostname, but using clear text HTTP) using the same cookie set
  3. The same cookie name is set - but with just a slash as path (path='/').
    Since this site is not secure, the cookie should just be ignored.
  4. A bug in the path comparison logic makes curl read outside a heap buffer
    boundary

The bug either causes a crash or it potentially makes the comparison come to
the wrong conclusion and lets the clear-text site override the contents of the
secure cookie, contrary to expectations and depending on the memory contents
immediately following the single-byte allocation that holds the path.

The presumed and correct behavior would be to plainly ignore the second set of
the cookie since it was already set as secure on a secure host so overriding
it on an insecure host should not be okay.

Severity

Moderate

References

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

@red-hat-konflux red-hat-konflux bot requested review from a team and rhacs-bot as code owners December 18, 2025 17:03
@github-actions github-actions bot added the backport PR to backport changes from master to release branch label Dec 18, 2025
@rhacs-bot
Copy link
Contributor

rhacs-bot commented Dec 18, 2025

Images are ready for the commit at 569dd61.

To use with deploy scripts, first export MAIN_IMAGE_TAG=4.7.9-1-g569dd617c8.

@codecov
Copy link

codecov bot commented Dec 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.05%. Comparing base (190eb4b) to head (569dd61).

Additional details and impacted files
@@               Coverage Diff               @@
##           release-4.7   #18292      +/-   ##
===============================================
- Coverage        49.06%   49.05%   -0.01%     
===============================================
  Files             2518     2518              
  Lines           183219   183219              
===============================================
- Hits             89889    89877      -12     
- Misses           86188    86198      +10     
- Partials          7142     7144       +2     
Flag Coverage Δ
go-unit-tests 49.05% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release-4.7/lock-file-maintenance-vulnerability branch 3 times, most recently from 254136e to 78ac566 Compare December 22, 2025 17:05
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release-4.7/lock-file-maintenance-vulnerability branch from 78ac566 to 569dd61 Compare December 22, 2025 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport PR to backport changes from master to release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant