Kiota: Path/URL injection into generated Copilot plugin manifest via x-ai-* extensions
microsoft kiota
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft.OpenApi.Kiota NuGet |
|
|
| Microsoft.OpenApi.Kiota.Builder NuGet |
|
microsoft kiota
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft.OpenApi.Kiota NuGet |
|
|
| Microsoft.OpenApi.Kiota.Builder NuGet |
|
|
Kiota is an OpenAPI based HTTP Client code generator. Prior to 1.29.1 and 1.32.5, `kiota plugin add` and `kiota plugin generate` (with `-t APIPlugin`) emitted attacker-controlled static_template.file values from x-ai-adaptive-card and x-ai-capabilities into generated Microsoft 365 Copilot and Teams plugin manifests without path validation, allowing ../, absolute, rooted, UNC, Windows drive, or URI paths in response_semantics.static_template.file to cause path traversal or out-of-package file inclusion when the generated plugin was deployed. This issue is fixed in version 1.29.1 and 1.32.5.
From the CVE record · GitHub_M
Kiota does not validate attacker-controlled static template file paths when generating Microsoft 365 Copilot and Teams plugin manifests with `kiota plugin add` or `kiota plugin generate -t APIPlugin`. If a generated plugin is deployed, those paths can cause path traversal or inclusion of files outside the plugin package.
Check users of the NuGet packages Microsoft.OpenApi.Kiota and Microsoft.OpenApi.Kiota.Builder on versions below 1.29.1 or from 1.30.0 up to, but not including, 1.32.5.