-
Notifications
You must be signed in to change notification settings - Fork 171
chore(deps): refresh rpm lockfiles [SECURITY] #18943
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
base: release-4.10
Are you sure you want to change the base?
chore(deps): refresh rpm lockfiles [SECURITY] #18943
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-4.10 #18943 +/- ##
================================================
- Coverage 49.39% 49.38% -0.01%
================================================
Files 2659 2659
Lines 200647 200647
================================================
- Hits 99101 99093 -8
- Misses 94106 94112 +6
- Partials 7440 7442 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Images are ready for the commit at cecf953. To use with deploy scripts, first |
|
@github-actions[bot]: The Use DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
1641008 to
76fc3fe
Compare
|
@github-actions[bot]: The Use DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@github-actions[bot]: The Use DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
76fc3fe to
cecf953
Compare
This PR contains the following updates:
File rpms.in.yaml:
3.12.12-1.el8_10->3.12.12-2.el8_103.12.12-1.el8_10->3.12.12-2.el8_101.0.6-3.el8->1.0.6-4.el8_102.9-10.el8_10->2.9-11.el8_102:2.29.0-3.el8_10.3->2:2.29.0-3.el8_10.42:2.29.0-3.el8_10.3->2:2.29.0-3.el8_10.42:2.29.0-3.el8_10.3->2:2.29.0-3.el8_10.4cpython: python: Python zipfile End of Central Directory (EOCD) Locator record offset not checked
CVE-2025-8291
More information
Details
The 'zipfile' module would not check the validity of the ZIP64 End of
Central Directory (EOCD) Locator record offset value would not be used to
locate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be
assumed to be the previous record in the ZIP archive. This could be abused
to create ZIP archives that are handled differently by the 'zipfile' module
compared to other ZIP implementations.
Remediation maintains this behavior, but checks that the offset specified
in the ZIP64 EOCD Locator record matches the expected value.
Severity
Moderate
References
cpython: Excessive read buffering DoS in http.client
CVE-2025-13836
More information
Details
A flaw was found in the http.client module in the Python standard library. When reading an HTTP response from a server, if no read amount is specified, the default behavior will be to use Content-Length. This issue allows a malicious server to cause the client to read large amounts of data into memory, potentially causing memory allocations errors, swapping, out-of-memory conditions or even system freezes.
Severity
Moderate
References
Scrapy: python-scrapy: brotli: Python brotli decompression bomb DoS
CVE-2025-6176
More information
Details
Scrapy are vulnerable to a denial of service (DoS) attack due to a flaw in its brotli decompression implementation. The protection mechanism against decompression bombs fails to mitigate the brotli variant, allowing remote servers to crash clients with less than 80GB of available memory. This occurs because brotli can achieve extremely high compression ratios for zero-filled data, leading to excessive memory consumption during decompression.
Severity
Important
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.
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.