| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/kcp-dev/kcp | < 0.28.3 | 0.28.3 |
Because UPDATE validation is not being applied, it is possible for an actor with access to an instance of the initializingworkspaces virtual workspace 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?
WorkspaceTypes with initializers that are inherited by other WorkspaceTypes.virtual/framework package to create their own virtualworkspaces if they are using UpdateFuncs in their custom storageWrappers.The issue occurs because the rest.ValidateObjectUpdateFunc 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.
The problem has been patched in #3599 and is available in kcp 0.28.3 and higher.
initialize verb on WorkspaceType objects (see documentation for details).WorkspaceType objects.See the pull request (#3599).
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free