CVE-2022-31055: Improper Access Control in kctf
First published: Mon Jun 13 2022(Updated: )
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.
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Kctf | <1.6.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-31055?
CVE-2022-31055 has been classified as a high-severity vulnerability due to its potential to allow unauthorized access.
How do I fix CVE-2022-31055?
To fix CVE-2022-31055, upgrade your kCTF installation to version 1.6.0 or later.
What impact does CVE-2022-31055 have on my kCTF environment?
CVE-2022-31055 allows traffic from any IP, which may expose your challenges to unauthorized access.
Is there a workaround for CVE-2022-31055 if I cannot upgrade?
Yes, you can configure your environment to restrict traffic manually as a temporary workaround.
Which versions are affected by CVE-2022-31055?
CVE-2022-31055 affects all versions of kCTF prior to version 1.6.0.
- collector/nvd-index
- agent/author
- agent/type
- agent/remedy
- agent/softwarecombine
- agent/references
- agent/weakness
- agent/description
- collector/nvd-api
- agent/software-canonical-lookup-request
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/title
- agent/event
- agent/first-publish-date
- agent/tags
- agent/source
- vendor/google
- canonical/google kctf