Chall-Manager's invalid NetworkPolicy enables a malicious actor to pivot into another namespace
ctfer-io chall-manager
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/ctfer-io/chall-manager/deploy Go |
|
|
| github.com/ctfer-io/chall-manager/sdk Go |
|
|
ctfer-io chall-manager
| Product | Affected | Fixed in |
|---|---|---|
| github.com/ctfer-io/chall-manager/deploy Go |
|
|
| github.com/ctfer-io/chall-manager/sdk Go |
|
|
Chall-Manager is a platform-agnostic system able to start Challenges on Demand of a player. In versions prior to 0.6.5, due to a miswritten NetworkPolicy, a malicious actor can pivot from an instance to any Pod out of the origin namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. In the specific case of sdk/kubernetes.Kompose it does not isolate the instances. This issue has been fixed in version 0.6.5.
From the CVE record · GitHub_M
Before 0.6.5, a miswritten NetworkPolicy lets an attacker pivot from a challenge instance to Pods outside its namespace. The sdk/kubernetes.Kompose implementation does not isolate instances. The input does not specify authentication or user-interaction requirements.
Teams running ctfer-io chall-manager with the Go deploy or sdk package before 0.6.5 should check their deployments.