-
Notifications
You must be signed in to change notification settings - Fork 3
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
chore(deps): update dependency cri-o/cri-o to v1.31.2 #8113
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Auto-approved because label type/renovate is present.
🔍 Vulnerabilities of
|
digest | sha256:da90dc1c876eaf1a3407050168fc0ef334dc8818c701a218e0343389ca88bd40 |
vulnerabilities | |
platform | linux/amd64 |
size | 19 MB |
packages | 192 |
stdlib
|
Affected range | <1.22.7 |
Fixed version | 1.22.7 |
Description
Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.
Affected range | <1.22.7 |
Fixed version | 1.22.7 |
Description
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.
Affected range | <1.22.7 |
Fixed version | 1.22.7 |
Description
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.
Affected range | <1.22.7 |
Fixed version | 1.22.7 |
Description
Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion.
github.com/opencontainers/runc 1.1.14
(golang)
pkg:golang/github.com/opencontainers/runc@1.1.14
OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities
Affected range | <1.2.0-rc.1 |
Fixed version | 1.2.0-rc.1 |
CVSS Score | 7.2 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Description
Withdrawn Advisory
This advisory has been withdrawn because it was incorrectly attributed to runc. Please see the issue here for more information.
Original Description
A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system. This issue has its root in how runc handles Config Annotations lists.
k8s.io/apiserver 0.31.0
(golang)
pkg:golang/k8s.io/apiserver@0.31.0
OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities
Affected range | <1.15.10 |
Fixed version | 1.15.10, 1.16.7, 1.17.3 |
CVSS Score | 4.3 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
Description
The Kubernetes API server component has been found to be vulnerable to a denial of service attack via successful API requests.
github.com/containers/common 0.60.3-0.20241001153533-18930ed8933b
(golang)
pkg:golang/github.com/containers/common@0.60.3-0.20241001153533-18930ed8933b
Improper Link Resolution Before File Access ('Link Following')
Affected range | <0.60.4 |
Fixed version | 0.60.4 |
CVSS Score | 5.4 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N |
Description
A flaw was found in Go. When FIPS mode is enabled on a system, container runtimes may incorrectly handle certain file paths due to improper validation in the containers/common Go library. This flaw allows an attacker to exploit symbolic links and trick the system into mounting sensitive host directories inside a container. This issue also allows attackers to access critical host files, bypassing the intended isolation between containers and the host system.
Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/11660465186. |
PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/11660465186. |
This PR contains the following updates:
1.31.1
->1.31.2
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
cri-o/cri-o (cri-o/cri-o)
v1.31.2
Compare Source
CRI-O v1.31.2
The release notes have been generated for the commit range
v1.31.1...v1.31.2 on Sat, 02 Nov 2024 00:21:02 UTC.
Downloads
Download one of our static release bundles via our Google Cloud Bucket:
To verify the artifact signatures via cosign, run:
To verify the bill of materials (SBOM) in SPDX format using the bom tool, run:
Changelog since v1.31.1
Changes by Kind
Uncategorized
allowed_annotation
specified twice (in either a workload or runtime) couldn't be used (#8710, @openshift-cherrypick-robot)Dependencies
Added
Nothing has changed.
Changed
Removed
Nothing has changed.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.