-
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 containers/podman to v4.8.2 #2046
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:596ff21508cd1c15699c21e51bdffce385564c0eac85d9e11044114e42d2e621 |
vulnerabilities | |
platform | linux/amd64 |
size | 33 MB |
packages | 168 |
github.com/opencontainers/runc
|
Affected range | <=v1.1.4 |
Fixed version | Not Fixed |
CVSS Score | 7 |
CVSS Vector | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Description
runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression.
Improper Preservation of Permissions
Affected range | <1.1.5 |
Fixed version | 1.1.5 |
CVSS Score | 6.1 |
CVSS Vector | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L |
Description
Impact
It was found that AppArmor, and potentially SELinux, can be bypassed when
/proc
inside the container is symlinked with a specific mount configuration.Patches
Fixed in runc v1.1.5, by prohibiting symlinked
/proc
: opencontainers/runc#3785This PR fixes CVE-2023-27561 as well.
Workarounds
Avoid using an untrusted container image.
Affected range | <1.1.2 |
Fixed version | 1.1.2 |
CVSS Score | 5.9 |
CVSS Vector | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
Description
Impact
A bug was found in runc where
runc exec --cap
executed processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2).This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set.
Patches
This bug has been fixed in runc 1.1.2. Users should update to this version as soon as possible.
This fix changes
runc exec --cap
behavior such that the additional capabilities granted to the process being executed (as specified via--cap
arguments) do not include inheritable capabilities.In addition,
runc spec
is changed to not set any inheritable capabilities in the created example OCI spec (config.json
) file.Credits
The opencontainers project would like to thank Andrew G. Morgan for responsibly disclosing this issue in accordance with the opencontainers org security policy.
For more information
If you have any questions or comments about this advisory:
- Open an issue
- Email us at security@opencontainers.org if you think you’ve found a security bug
Improper Preservation of Permissions
Affected range | <1.1.5 |
Fixed version | 1.1.5 |
CVSS Score | 2.5 |
CVSS Vector | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:N/A:L |
Description
Impact
It was found that rootless runc makes
/sys/fs/cgroup
writable in following conditons:
- when runc is executed inside the user namespace, and the
config.json
does not specify the cgroup namespace to be unshared (e.g..,(docker|podman|nerdctl) run --cgroupns=host
, with Rootless Docker/Podman/nerdctl)- or, when runc is executed outside the user namespace, and
/sys
is mounted withrbind, ro
(e.g.,runc spec --rootless
; this condition is very rare)A container may gain the write access to user-owned cgroup hierarchy
/sys/fs/cgroup/user.slice/...
on the host .
Other users's cgroup hierarchies are not affected.Patches
v1.1.5 (planned)
Workarounds
- Condition 1: Unshare the cgroup namespace (
(docker|podman|nerdctl) run --cgroupns=private)
. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts.- Condition 2 (very rare): add
/sys/fs/cgroup
tomaskedPaths
k8s.io/kubernetes 1.28.4
(golang)
pkg:golang/k8s.io/kubernetes@1.28.4
OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities
Affected range | >1.16 |
Fixed version | 1.16 |
CVSS Score | 6.5 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N |
Description
Improper input validation in Kubernetes CSI sidecar containers for external-provisioner (<v0.4.3, <v1.0.2, v1.1, <v1.2.2, <v1.3.1), external-snapshotter (<v0.4.2, <v1.0.2, v1.1, <1.2.2), and external-resizer (v0.1, v0.2) could result in unauthorized PersistentVolume data access or volume mutation during snapshot, restore from snapshot, cloning and resizing operations.
Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/7170510160. |
PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/7170510160. |
This PR contains the following updates:
4.8.1
->4.8.2
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
containers/podman (containers/podman)
v4.8.2
Compare Source
Bugfixes
Quadlet
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.