-
Notifications
You must be signed in to change notification settings - Fork 1.1k
server: filter sysctls passed through CRI if host namespace #5610
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
server: filter sysctls passed through CRI if host namespace #5610
Conversation
Signed-off-by: Peter Hunt <pehunt@redhat.com>
Signed-off-by: Peter Hunt <pehunt@redhat.com>
running CI here to make sure nothing unexpected fails |
Codecov Report
@@ Coverage Diff @@
## main #5610 +/- ##
==========================================
- Coverage 43.24% 43.22% -0.03%
==========================================
Files 123 123
Lines 12220 12224 +4
==========================================
- Hits 5285 5284 -1
- Misses 6427 6432 +5
Partials 508 508 |
/test integration_rhel |
/retest-required |
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.
LGTM
although I am not sure about the security implications. For using a host namespace, the container is already privileged. AFAIK, runc has already the same check and it was added to the last release of crun as well.
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fgiudici, giuseppe, haircommander The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest-required Please review the full test history for this PR and help us cut down flakes. |
yeah I waiver between this being moderate and low severity. most kubernetes clusters don't do anything to prevent users from using host namespaces (until updated PSP, which is fairly new), which makes it more nefarious for upstream consumers (OCP has SCC, which mitigates this). However, the underlying principle is that a container affects the host in a way that wasn't really intended, which does feel like a container breakout |
/cherry-pick release-1.23 |
@haircommander: once the present PR merges, I will cherry-pick it on top of release-1.23 in a new PR and assign it to you. In 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/test-infra repository. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@haircommander: The following test failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
/override ci/prow/e2e-agnostic |
@haircommander: Overrode contexts on behalf of haircommander: ci/prow/e2e-agnostic In 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/test-infra repository. |
/override ci/openshift-jenkins/integration_rhel |
@haircommander: Overrode contexts on behalf of haircommander: ci/openshift-jenkins/integration_rhel In 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/test-infra repository. |
@haircommander: new pull request created: #5615 In 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/test-infra repository. |
/cherry-pick release-1.22 |
@haircommander: new pull request created: #5616 In 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/test-infra repository. |
/cherry-pick release-1.21 |
@haircommander: #5610 failed to apply on top of branch "release-1.21":
In 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/test-infra repository. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
fixes GHSA-w2j5-3rcx-vx7x
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?