fix: disable privileged mode on web container - #120
Open
hacktron-app-stg[bot] wants to merge 1 commit into
Open
Conversation
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.yamlconfigured thewebcontainer withsecurityContext.privileged: true. A privileged container disables key security protections and gains near-full access to the host's devices and kernel capabilities, allowing container escape and host compromise (critical severity).Fix
Set
privileged: falsein the container'ssecurityContext, removing the elevated host access. This is a minimal, targeted change to the reported finding atdeployment.yaml:23.Verification
Confirmed via
grepthat the manifest now declaresprivileged: false. No YAML tooling was installed in the sandbox, but the edit is a single field value change and leaves the manifest structurally valid (verified by inspection). Other manifest hardening issues (hostNetwork/hostPID, runAsUser 0, hardcoded secret, host-root mount) are tracked as separate findings and intentionally not modified here.Automated fix by Hacktron for finding: https://staging.hacktron.ai/testestesttest/findings/4c215f42-8942-4f81-88d7-537d26999619