fix: remove full host filesystem hostPath mount from web deployment#119
Open
hacktron-app-stg[bot] wants to merge 1 commit into
Open
fix: remove full host filesystem hostPath mount from web deployment#119hacktron-app-stg[bot] wants to merge 1 commit into
hacktron-app-stg[bot] wants to merge 1 commit into
Conversation
The web container mounted the host root (`hostPath: /`) at `/host`, granting read/write access to the entire node filesystem and enabling full host compromise. Removed the volume and its volumeMount since no code referenced it.
hacktron-app-stg
Bot
force-pushed
the
hacktron/fix-357b40ea
branch
from
July 23, 2026 09:19
5af598e to
ccab0e2
Compare
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.yamlmounted the entire host root filesystem into thewebcontainer:A
hostPathvolume withpath: /gives the container read/write access to every file on the underlying node — kernel/config/secrets, other containers' data, kubelet credentials, etc. Combined with the container's privileged settings this allows trivial full host compromise. Severity: critical.Fix
Removed the
host-roothostPathvolume and itsvolumeMount. The mount was not referenced by any application code or configuration, so it can be dropped safely without a functional replacement.Verification
host-rootvolume or/hostmount path.deployment.yamlis structurally intact YAML (thecontainerslist now terminates at theenvblock; no danglingvolumeMounts/volumeskeys remain).Note: this PR intentionally addresses only the reported "Full Host Filesystem Mount" finding. Other insecure settings present in the manifest (privileged, hostNetwork/hostPID, runAsUser 0, hardcoded secret,
:latestimage) are separate findings and out of scope for this change.Automated fix by Hacktron for finding: https://staging.hacktron.ai/testestesttest/findings/357b40ea-46a3-453e-9e47-51829fca59e4