chore(deps): update dependency nestybox/sysbox to v0.6.5

[uniget-bot]

This PR contains the following updates:

Package	Update	Change
nestybox/sysbox	patch	0.6.4 -> 0.6.5

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

nestybox/sysbox (nestybox/sysbox)

v0.6.5

Compare Source

Added

• Update to Golang 1.22.
• Implement 'relaxed-read-only' mode to ease the bind-mount requirements of read-only containers.
• Enhance sysbox-fs emulation to allow writes to '/proc/sys/kernel/shm*' paths.
• Fix emulation of /proc/sys/kernel/random (issue #​785).
• Fix bug in sysbox-fs that resulted in left-over nsenter mounts of procfs and sysfs (issue #​829).
• Fix issue causing Sysbox to slow down due to the accumulation of large numbers of mountpoints when '--allow-immutable-unmounts' knob is set to 'false'.
• Skip dns change when default route doesn't exists (issue #​834).
• Fix issue breaking read() operations over '/sys/kernel' nodes with non-zero offsets.
• Return error for disallowed unmount of sysbox-fs managed mountpoint (issue #​808).
• sysbox-deploy-k8s: add support for K8s v1.29 and v1.30.
• sysbox-deploy-k8s: deprecate support of K8s v1.26.
• sysbox-deploy-k8s: add support for incremental Sysbox upgrades.
• sysbox-deploy-k8s: introduce logic to config Sysbox's daemons through a configMap.
• sysbox-deploy-k8s: increase 'vm.max_map_count' to satisfy mmap-demanding apps (Elastic).
• sysbox-deploy-k8s: enhance logic to detect Sysbox's config-environment changes (sysctl vars).
• sysbox-deploy-k8s: fix issue preventing Sysbox installation from concluding during upgrades.
• sysbox-deploy-k8s: fix for race-condition in GKE clusters.
• sysbox-deploy-k8s: fix for 'sysbox-installer-helper' to workaround dpkg error.
• sysbox-deploy-k8s: check for existence of 'unprivileged_userns_clone' procfs node before attempting to write().
• sysbox-deploy-k8s: delete preexisting sysbox pods during upgrade or re-installation process.

---

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.

---

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

---

This PR has been generated by Renovate Bot.

[nicholasdille-bot]

Auto-approved because label type/renovate is present.

[github-actions]

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/sysbox:0.6.5

📦 Image Reference ghcr.io/uniget-org/tools/sysbox:0.6.5

digest	sha256:02d63546e999075982ab9c906191e7cb36808f6588e16eed28aa54901f8e0a22
vulnerabilities
platform	linux/amd64
size	18 MB
packages	74

github.com/docker/docker 26.0.0+incompatible (golang) pkg:golang/github.com/docker/[email protected]+incompatible Partial String Comparison Affected range >=26.0.0 <26.1.5 Fixed version 26.1.5 CVSS Score 9.9 CVSS Vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H Description A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low. This advisory outlines the issue, identifies the affected versions, and provides remediation steps for impacted users. Impact Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an authorization plugin without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it. A security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine v18.09.1 in January 2019, the fix was not carried forward to later major versions, resulting in a regression. Anyone who depends on authorization plugins that introspect the request and/or response body to make access control decisions is potentially impacted. Docker EE v19.03.x and all versions of Mirantis Container Runtime are not vulnerable. Vulnerability details AuthZ bypass and privilege escalation: An attacker could exploit a bypass using an API request with Content-Length set to 0, causing the Docker daemon to forward the request without the body to the AuthZ plugin, which might approve the request incorrectly. Initial fix: The issue was fixed in Docker Engine v18.09.1 January 2019.. Regression: The fix was not included in Docker Engine v19.03 or newer versions. This was identified in April 2024 and patches were released for the affected versions on July 23, 2024. The issue was assigned CVE-2024-41110. Patches docker-ce v27.1.1 containes patches to fix the vulnerability. Patches have also been merged into the master, 19.0, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches. Remediation steps If you are running an affected version, update to the most recent patched version. Mitigation if unable to update immediately: Avoid using AuthZ plugins. Restrict access to the Docker API to trusted parties, following the principle of least privilege. References moby/moby@fc274cd moby/moby@a79fabb https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin/ Exposure of Resource to Wrong Sphere Affected range >=26.0.0 <26.0.2 Fixed version 26.0.2 CVSS Score 4.7 CVSS Vector CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N Description In 26.0.0 and 26.0.1, IPv6 is not disabled on network interfaces, including those belonging to networks where --ipv6=false. Impact A container with an ipvlan or macvlan interface will normally be configured to share an external network link with the host machine. Because of this direct access, with IPv6 enabled: Containers may be able to communicate with other hosts on the local network over link-local IPv6 addresses. If router advertisements are being broadcast over the local network, containers may get SLAAC-assigned addresses. The interface will be a member of IPv6 multicast groups. This means interfaces in IPv4-only networks present an unexpectedly and unnecessarily increased attack surface. A container with an unexpected IPv6 address can do anything a container configured with an IPv6 address can do. That is, listen for connections on its IPv6 address, open connections to other nodes on the network over IPv6, or attempt a DoS attack by flooding packets from its IPv6 address. This has CVSS score AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:N/A:L (2.7). Because the container may not be constrained by an IPv6 firewall, there is increased potential for data exfiltration from the container. This has CVSS score AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N (4.7). A remote attacker could send malicious Router Advertisements to divert traffic to itself, a black-hole, or another device. The same attack is possible today for IPv4 macvlan/ipvlan endpoints with ARP spoofing, TLS is commonly used by Internet APIs to mitigate this risk. The presence of an IPv6 route could impact the container's availability by indirectly abusing the behaviour of software which behaves poorly in a dual-stack environment. For example, it could resolve a name to a DNS AAAA record and keep trying to connect over IPv6 without ever falling back to IPv4, potentially denying service to the container. This has CVSS score AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H (4.5). Patches The issue is patched in 26.0.2. Workarounds To completely disable IPv6 in a container, use --sysctl=net.ipv6.conf.all.disable_ipv6=1 in the docker create or docker run command. Or, in the service configuration of a compose file, the equivalent: sysctls: - net.ipv6.conf.all.disable_ipv6=1 References sysctl configuration using docker run: https://docs.docker.com/reference/cli/docker/container/run/#sysctl sysctl configuration using docker compose: https://docs.docker.com/compose/compose-file/compose-file-v3/#sysctls

github.com/cyphar/filepath-securejoin 0.2.2 (golang) pkg:golang/github.com/cyphar/[email protected] Affected range <0.2.4 Fixed version 0.2.4 Description Impact For Windows users of github.com/cyphar/filepath-securejoin, until v0.2.4 it was possible for certain rootfs and path combinations (in particular, where a malicious Unix-style /-separated unsafe path was used with a Windows-style rootfs path) to result in generated paths that were outside of the provided rootfs. It is unclear to what extent this has a practical impact on real users, but given the possible severity of the issue we have released an emergency patch release that resolves this issue. Thanks to @pjbgf for discovering, debugging, and fixing this issue (as well as writing some tests for it). Patches c121231e1276e11049547bee5ce68d5a2cfe2d9b is the patch fixing this issue. v0.2.4 contains the fix. Workarounds Users could use filepath.FromSlash() on all unsafe paths before passing them to filepath-securejoin. References See #9.

google.golang.org/grpc 1.64.0 (golang) pkg:golang/google.golang.org/[email protected] Exposure of Sensitive Information to an Unauthorized Actor Affected range >=1.64.0 <1.64.1 Fixed version 1.64.1 Description Impact This issue represents a potential PII concern. If applications were printing or logging a context containing gRPC metadata, the affected versions will contain all the metadata, which may include private information. Patches The issue first appeared in 1.64.0 and is patched in 1.64.1 and 1.65.0 Workarounds If using an affected version and upgrading is not possible, ensuring you do not log or print contexts will avoid the problem.

[github-actions]

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/11761278485.

[github-actions]

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/11761278485.