KEDA has Arbitrary File Read via Insufficient Path Validation in HashiCorp Vault Service Account Credential
kedacore keda
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kedacore/keda/v2 Go |
|
|
| github.com/kedacore/keda Go |
| No fix yet |
kedacore keda
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kedacore/keda/v2 Go |
|
|
| github.com/kedacore/keda Go |
| No fix yet |
KEDA is a Kubernetes-based Event Driven Autoscaling component. Prior to versions 2.17.3 and 2.18.3, an Arbitrary File Read vulnerability has been identified in KEDA, potentially affecting any KEDA resource that uses TriggerAuthentication to configure HashiCorp Vault authentication. The vulnerability stems from an incorrect or insufficient path validation when loading the Service Account Token specified in spec.hashiCorpVault.credential.serviceAccount. An attacker with permissions to create or modify a TriggerAuthentication resource can exfiltrate the content of any file from the node's filesystem (where the KEDA pod resides) by directing the file's content to a server under their control, as part of the Vault authentication request. The potential impact includes the exfiltration of sensitive system information, such as secrets, keys, or the content of files like /etc/passwd. This issue has been patched in versions 2.17.3 and 2.18.3.
From the CVE record · GitHub_M
KEDA can read unintended files when a TriggerAuthentication resource configures HashiCorp Vault authentication with a Service Account Token. An attacker with permission to create or modify that resource can cause the KEDA pod to send files from its node’s filesystem to an attacker-controlled server during Vault authentication; no other user interaction is described.
Check deployments using github.com/kedacore/keda/v2 versions before 2.17.3 or versions 2.18.0 through 2.18.2, and users of github.com/kedacore/keda, for which no fixed version is listed.