Security readout for executives and security teams
Plain-English summary
kCTF deployments before 1.6.0 could fail to enforce source-IP restrictions for challenge traffic. Teams that believed a challenge was reachable only from approved IP ranges may have exposed it to anyone on the internet. The core business risk is unintended disclosure of private challenge content or test infrastructure.
Executive priority
Prioritize remediation if your organization runs kCTF for private challenge development, internal competitions, or pre-release testing. The fix is clear and the exposure could undermine confidentiality assumptions, but evidence of real-world exploitation was not provided.
Technical view
The vulnerable kCTF cluster set-src-ip-ranges feature did not properly restrict traffic before version 1.6.0, allowing access from any IP. The CVSS vector is network exploitable, low complexity, unauthenticated, and high confidentiality impact. The issue is patched in v1.6.0.
Likely exposure
Exposure is likely limited to organizations using Google kCTF before 1.6.0 and relying on set-src-ip-ranges to restrict challenge access. Public CTF challenges intentionally exposed to the internet are less affected by this specific control failure.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked as KEV. The weakness is still operationally serious because a broken access-control setting could silently expose private CTF challenges or testing environments without authentication.
Researcher notes
Focus validation on whether set-src-ip-ranges was used as the primary access boundary before v1.6.0. Treat any reachable private challenge endpoint as a confidentiality exposure. The source bundle does not provide deeper affected configuration details beyond kCTF versions before 1.6.0.
Mitigation direction
- Upgrade kCTF deployments to version 1.6.0 or later.
- For private testing, mark challenges as public: false.
- Use the vendor-documented debug port-forward workflow for private challenge access.
- Check vendor guidance before applying alternative network-control assumptions.
Validation and detection
- Inventory kCTF deployments and confirm no instance runs earlier than 1.6.0.
- Identify challenge configurations that relied on set-src-ip-ranges restrictions.
- Verify restricted challenges are not reachable from untrusted external networks.
- Review logs for unexpected external IPs hitting private challenge endpoints.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-31055 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/google/kctf/security/advisories/GHSA-4g2v-6qc6-6jv5CVE reference · x_refsource_CONFIRM
- https://github.com/google/kctf/pull/371CVE reference · x_refsource_MISC
- https://github.com/google/kctf/commit/8cf050be974fcc2fd8aa136701f9a66f2b2a5202CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.