Vulnerabilities

Kiteworks Core contains a business logic flaw in a Kiteworks file-request feature allowed an authenticated user to send a request that appeared to originate from another user, because the server did not verify that the r…

An endpoint used during initial appliance setup did not require authentication and did not correctly enforce its intended state precondition, so during the initial activation window an unauthenticated network attacker co…

On deployments where the remote-support capability is licensed and enabled, an authenticated System Administrator who also possessed the key protecting the submitted data could redirect the underlying system's outbound s…

A privilege escalation vulnerability in Kiteworks could have allowed an attacker who had already obtained code execution on one node of a clustered Kiteworks deployment to run operating system commands with elevated priv…

Kiteworks did not correctly enforce which roles a shared folder's manager was permitted to assign.

A stored cross-site scripting (XSS) weakness in Kiteworks Core could allow an administrator holding only a single, narrowly scoped delegated permission to store crafted content that later executes arbitrary JavaScript in…

A user-provisioning interface in Kiteworks Core did not verify that the requesting administrator was entitled to grant the role being assigned.

An administrative import function in Kiteworks Core did not verify that the requesting administrator was entitled to create the privileged integration credential being imported.

An optional, separately licensed repository-connector feature in Kiteworks Core did not neutralize special characters in a user-supplied path before passing it to an external command.

Kiteworks Core did not apply its gateway-level API security controls to every request authenticated through the platform's central authentication service.

In multi-node deployments, an attacker who had already obtained code execution on one appliance node could submit a value through an internal cluster interface that was written into monitoring configuration on another no…

An authenticated administrator could bypass the content validation applied to an administrative file upload and store a file containing dangerous content on the appliance.

An authenticated administrator on a node with an optional, separately licensed gateway role enabled could supply a connector URL that the server retrieved without sufficient validation of its scheme or destination, causi…

An authenticated administrator could initiate an administrative import using a file whose contents were not fully verified, because the import validated only the file's header rather than the complete file.

Two Kiteworks Core cluster-management operations did not validate file paths supplied to them, so an attacker holding root on one node of a cluster could write files as root onto another node and cause them to be execute…

A system notification template on the Kiteworks appliance was rendered by a template engine that evaluated expressions contained in the stored template body.

A stored cross-site scripting (XSS) weakness in Kiteworks Core could allow an unauthenticated attacker to store crafted content that later executes arbitrary JavaScript in the authenticated session of an administrator wh…

An authenticated administrator could cause the server to issue requests to, and interact with, internal network services that are not meant to be reachable through this interface.

Kiteworks Core before version 9.5.1 is vulnerable to Content Injection.