fix: disable host network and PID namespace sharing in deployment#117
Open
hacktron-app-stg[bot] wants to merge 1 commit into
Open
fix: disable host network and PID namespace sharing in deployment#117hacktron-app-stg[bot] wants to merge 1 commit into
hacktron-app-stg[bot] wants to merge 1 commit into
Conversation
Set hostNetwork and hostPID to false in deployment.yaml to prevent the container from sharing the host node's network and process namespaces, which allowed host traffic interception and host process visibility.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vulnerability
deployment.yamlsethostNetwork: trueandhostPID: trueon the pod spec (lines 16-17). This merges the container's network and process namespaces with the host node's, allowing the container to:hostPID: true).hostNetwork: true).This is a high-severity container-isolation weakness.
Fix
Changed both flags to
false, restoring standard namespace isolation between the pod and the host node:These values match the Kubernetes defaults, so the container now runs in its own network and PID namespaces.
Verification
Reviewed the manifest before and after the change; the pod spec no longer opts into host namespaces. Change is minimal and scoped strictly to the reported finding. The repository contains no test infrastructure for Kubernetes manifests, so no automated regression test was added.
Automated fix by Hacktron for finding: https://staging.hacktron.ai/testestesttest/findings/42e72c42-3d3f-4299-892b-800455c319cc