GHSA-q6hv-wcjr-wp8h: Github.com/kcp dev/kcp Kcp Is Missing Update Validation Vulnerability

LOW
CWE-285
Published
Advisory Summary

GHSA-q6hv-wcjr-wp8h is a LOW kcp is missing update validation vulnerability (CWE-285: Improper Authorization) affecting Github.com/kcp dev/kcp libraries in the Go ecosystem. The issue involves kcp is missing update validation allows arbitrary logicalcluster status patches through initializingworkspaces virtual workspace. Remediation is available by upgrading affected packages to version 0.28.3.

GHSA-q6hv-wcjr-wp8h at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-q6hv-wcjr-wp8h
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-285: Improper Authorization
Affected Product Github.com/kcp dev/kcp
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-q6hv-wcjr-wp8h

To remediate this vulnerability, upgrade all affected Github.com/kcp dev/kcp dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/kcp-dev/kcp fixed: 0.28.3
Upgrade github.com/kcp-dev/kcp to 0.28.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/kcp-dev/kcp

How to Check if You Are Affected

To determine whether your application is affected by GHSA-q6hv-wcjr-wp8h, inspect your project dependencies for Github.com/kcp dev/kcp:

inspect dependencies for github.com/kcp-dev/kcp

Analyze the terminal output to locate any version of Github.com/kcp dev/kcp in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.28.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. In Github.com/kcp dev/kcp, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Because UPDATE validation is not being applied, it is possible for an actor with access to an instance of the [initializingworkspaces virtual workspace](https://docs.kcp.io/kcp/latest/concepts/workspaces/workspace-initialization/) to run arbitrary patches on the status field of `LogicalCluster` objects while the workspace is initializing. This allows to add or remove any initializers as well as changing the phase of a `LogicalCluster` (to "Ready" for example). As this effectively allows to skip certain initializers or the entire initialization phase, potential integrations with external systems such as billing or security could be affected. Their initializers could be skipped by a `WorkspaceType` that adds another initializer and grants permissions to the virtual workspace to a rogue or compromised entity. _Who is impacted?_ * Impacts other owners of `WorkspaceTypes` with initializers that are inherited by other `WorkspaceTypes`. * Impacts developers using the `virtual/framework` package to create their own virtualworkspaces if they are using UpdateFuncs in their custom storageWrappers. ### Details The issue occurs because the [rest.ValidateObjectUpdateFunc](https://github.com/kcp-dev/kcp/blob/cli/v0.28.1/pkg/virtual/framework/forwardingregistry/store.go#L174) is not being called within the DefaultDynamicDelegatedStoreFuncs. As a result, the intended status overwrite protection from initializers never gets called, allowing arbitrary logicalcluster status patches. ### Patches The problem has been patched in #3599 and is available in kcp 0.28.3 and higher. ### Workarounds - Further limit access to the `initialize` verb on `WorkspaceType` objects (see [documentation](https://docs.kcp.io/kcp/v0.28/concepts/workspaces/workspace-initialization/#enforcing-permissions-for-initializers) for details). - Only use trusted `WorkspaceType` objects. ### References See the pull request (#3599).

GHSA-q6hv-wcjr-wp8h Affected Github.com/kcp dev/kcp Versions

1 component(s)
Fixed Versions:
0.28.3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/kcp-dev/kcp
Go
< 0.28.3
0.28.3

References

Frequently Asked Questions

What is GHSA-q6hv-wcjr-wp8h?
GHSA-q6hv-wcjr-wp8h is a security vulnerability in Github.com/kcp dev/kcp involving kcp is missing update validation allows arbitrary LogicalCluster status patches through initializingworkspaces Virtual Workspace under CWE-285: Improper Authorization.
Which Github.com/kcp dev/kcp versions are affected?
Affected versions include releases prior to 0.28.3 across affected packages: github.com/kcp-dev/kcp.
What version fixes GHSA-q6hv-wcjr-wp8h?
Upgrading to 0.28.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/kcp-dev/kcp affected?
Yes, github.com/kcp-dev/kcp is affected in releases prior to 0.28.3. Upgrade your dependency to 0.28.3 or later.
What CWE is associated with GHSA-q6hv-wcjr-wp8h?
GHSA-q6hv-wcjr-wp8h is classified under CWE-285: Improper Authorization (The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Go dependencies for GHSA-q6hv-wcjr-wp8h?
Run the dependency tree command: 'inspect dependencies for github.com/kcp-dev/kcp'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q6hv-wcjr-wp8h",
  "modified" : "2025-10-23T20:15:01Z",
  "published" : "2025-09-26T15:00:19Z",
  "aliases" : [ ],
  "summary" : "kcp is missing update validation allows arbitrary LogicalCluster status patches through initializingworkspaces Virtual Workspace",
  "details" : "### Impact\n\nBecause UPDATE validation is not being applied, it is possible for an actor with access to an instance of the [initializingworkspaces virtual workspace](https://docs.kcp.io/kcp/latest/concepts/workspaces/workspace-initialization/) to run arbitrary patches on the status field of `LogicalCluster` objects while the workspace is initializing.\n\nThis allows to add or remove any initializers as well as changing the phase of a `LogicalCluster` (to \"Ready\" for example).\n\nAs this effectively allows to skip certain initializers or the entire initialization phase, potential integrations with external systems such as billing or security could be affected. Their initializers could be skipped by a `WorkspaceType` that adds another initializer and grants permissions to the virtual workspace to a rogue or compromised entity.\n\n_Who is impacted?_\n\n* Impacts other owners of `WorkspaceTypes` with initializers that are inherited by other `WorkspaceTypes`.\n* Impacts developers using the `virtual/framework` package to create their own virtualworkspaces if they are using UpdateFuncs in their custom storageWrappers.\n\n### Details\n\nThe issue occurs because the [rest.ValidateObjectUpdateFunc](https://github.com/kcp-dev/kcp/blob/cli/v0.28.1/pkg/virtual/framework/forwardingregistry/store.go#L174) is not being called within the DefaultDynamicDelegatedStoreFuncs. As a result, the intended status overwrite protection from initializers never gets called, allowing arbitrary logicalcluster status patches.\n\n### Patches\n\nThe problem has been patched in #3599 and is available in kcp 0.28.3 and higher.\n\n### Workarounds\n\n- Further limit access to the `initialize` verb on `WorkspaceType` objects (see [documentation](https://docs.kcp.io/kcp/v0.28/concepts/workspaces/workspace-initialization/#enforcing-permissions-for-initializers) for details).\n- Only use trusted `WorkspaceType` objects.\n\n### References\n\nSee the pull request (#3599).",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/kcp-dev/kcp"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.28.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.28.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/kcp-dev/kcp/security/advisories/GHSA-q6hv-wcjr-wp8h"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kcp-dev/kcp/pull/3599"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kcp-dev/kcp/commit/02134a2a51d33652ab288cccd7a13539b59c7584"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/kcp-dev/kcp"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kcp-dev/kcp/releases/tag/v0.28.3"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2025-3985"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-285" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-09-26T15:00:19Z",
    "nvd_published_at" : null
  }
}