Skip to content
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-tui to v0.13.0 #1901

Merged
merged 1 commit into from
Dec 1, 2023

Conversation

uniget-bot
Copy link

This PR contains the following updates:

Package Update Change
containers/podman-tui minor 0.12.0 -> 0.13.0

Warning

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


Release Notes

containers/podman-tui (containers/podman-tui)

v0.13.0

Compare Source

  • Adding container create mount inputfield option
  • Use inputfield for container create volume option
  • EPEL rpm package
  • Github action update
  • Docs update - add Gentoo in packaged versions
  • Running golangci-lint on ui package
  • Running golangci-lint on app package
  • Running golangci-lint on config package
  • Running golangci-lint on cmd package
  • Bump github.com/containers/podman/v4 from 4.7.2 to 4.8.0
  • Bump golang.org/x/crypto from 0.15.0 to 0.16.0
  • Bump github.com/navidys/tvxwidgets from 0.4.0 to 0.4.1
  • Bump github.com/go-jose/go-jose/v3 from 3.0.0 to 3.0.1
  • Bump github.com/containers/storage from 1.50.2 to 1.51.0

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.

Copy link

@nicholasdille-bot nicholasdille-bot left a 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.

Copy link

github-actions bot commented Dec 1, 2023

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/podman-tui:0.13.0

📦 Image Reference ghcr.io/uniget-org/tools/podman-tui:0.13.0
digestsha256:c70e1f4eaf608a8a37e478801d0cfcbf51e4bfc194ea8da96b1382e14297d8d0
vulnerabilitiescritical: 0 high: 1 medium: 2 low: 2
platformlinux/amd64
size13 MB
packages75
critical: 0 high: 1 medium: 2 low: 1 github.com/opencontainers/runc 1.1.1-0.20220617142545-8b9452f75cbc (golang)

pkg:golang/github.com/opencontainers/[email protected]

high 7.0: CVE--2023--27561 OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities

Affected range<=v1.1.4
Fixed versionNot Fixed
CVSS Score7
CVSS VectorCVSS: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.

medium 6.1: CVE--2023--28642 Improper Preservation of Permissions

Affected range<1.1.5
Fixed version1.1.5
CVSS Score6.1
CVSS VectorCVSS: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#3785

This PR fixes CVE-2023-27561 as well.

Workarounds

Avoid using an untrusted container image.

medium 5.9: CVE--2022--29162 Incorrect Default Permissions

Affected range<1.1.2
Fixed version1.1.2
CVSS Score5.9
CVSS VectorCVSS: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:

low 2.5: CVE--2023--25809 Improper Preservation of Permissions

Affected range<1.1.5
Fixed version1.1.5
CVSS Score2.5
CVSS VectorCVSS: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:

  1. 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)
  2. or, when runc is executed outside the user namespace, and /sys is mounted with rbind, 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 to maskedPaths
critical: 0 high: 0 medium: 0 low: 1 github.com/containers/podman/v4 4.8.0 (golang)

pkg:golang/github.com/containers/podman/[email protected]

low : CVE--2022--4123

Affected range>=4.1.0-rc1
Fixed versionNot Fixed
Description

The local path and the lowest subdirectory may be disclosed due to incorrect absolute path traversal, resulting in an impact to confidentiality.

Copy link

github-actions bot commented Dec 1, 2023

Copy link

github-actions bot commented Dec 1, 2023

@github-actions github-actions bot merged commit bfb532e into main Dec 1, 2023
8 checks passed
@github-actions github-actions bot deleted the renovate/containers-podman-tui-0.x branch December 1, 2023 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants