Summary
Fullchain versions prior to 0.1.1 contain a mis-written Kubernetes NetworkPolicy that may fail to enforce the intended network access restrictions.
A malicious actor who can reach the affected deployment may be able to access network paths that should be restricted, depending on the platform's surrounding Kubernetes configuration.
Affected context
The issue occurs in Fullchain, an umbrella project used to deploy a ready-to-use CTF platform, when its Kubernetes NetworkPolicy is applied with incorrect rules. The risk depends on how the policy is interpreted by the cluster's network plugin and whether other authentication, segmentation, or service-level controls provide additional protection.
Exploit preconditions
- Attack surface: Network connectivity to services or workloads governed by the affected policy
- Required access: Ability to send traffic through a network path that the policy should restrict
- Trigger point: Evaluation of the misconfigured NetworkPolicy by the Kubernetes networking layer
- Why exploitation is possible: Incorrect policy rules may permit unintended ingress or egress instead of enforcing the intended isolation
Why this happens
The underlying issue is an incorrectly written network access-control policy. Kubernetes NetworkPolicies define which traffic may reach selected workloads, and errors in selectors, directions, ports, or allow rules can cause the effective policy to differ from the intended security boundary.
This maps to CWE-284: Improper Access Control, because network access is not restricted consistently with the deployment's intended authorization rules.
Potential impact
- An attacker may reach services or workloads that should be isolated
- Unauthorized network access could expose administrative or internal interfaces
- An attacker could use permitted connectivity for reconnaissance or lateral movement
- Sensitive application data or challenge infrastructure could be placed at greater risk
General mitigation guidance
Mitigation generally focuses on making network authorization explicit, minimal, and independently validated.
Common defensive patterns include:
- Define default-deny ingress and egress behavior where operationally appropriate
- Use narrowly scoped workload selectors, namespaces, ports, and traffic directions
- Reduce reliance on broad labels or unrestricted allow rules
- Combine NetworkPolicies with service authentication, authorization, and segmentation controls
- Run workloads with least privilege and limit access to administrative services
- Validate effective policy behavior in staging and enforce policy checks in deployment pipelines
How teams detect issues like this
Organizations can look for this class of issue through:
- Static review of NetworkPolicy selectors, namespaces, ports, and ingress or egress rules
- Code review checks for broad allow rules, missing default-deny policies, and selector mismatches
- Automated policy validation and admission controls that require approved network-segmentation patterns
- Runtime testing that verifies both permitted and denied traffic paths
- Monitoring for unexpected connections between namespaces, services, and administrative endpoints

