Kiota: Code Generation Literal Injection
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. Versions prior to 1.29.1 and 1.31.1 are affected by a code-generation literal injection vulnerability in multiple writer sinks (for example: serialization/deserialization keys, path/query parameter mappings, URL template metadata, enum/property metadata, and default value emission). When malicious values from an OpenAPI description are emitted into generated source without context-appropriate escaping, an attacker can break out of string literals and inject additional code into generated clients. This issue is only practically exploitable when the OpenAPI description used for generation is from an untrusted source, or a normally trusted OpenAPI description has been compromised/tampered with. Only generating from trusted, integrity-protected API descriptions significantly reduces the risk. To remediate the issue, upgrade Kiota to 1.29.1, 1.31.1, or later and regenerate/refresh existing generated clients as a precaution. Refreshing generated clients ensures previously generated vulnerable code is replaced with hardened output.
From the CVE record · GitHub_M
Kiota can emit malicious values from an OpenAPI description into generated client source without properly escaping them. An attacker can inject code into generated clients if the description used for generation is untrusted or has been tampered with. Exploitation requires generating a client from that description; authentication requirements are not specified.
Teams using the NuGet packages Microsoft.OpenApi.Kiota or Microsoft.OpenApi.Kiota.Builder in versions below 1.29.1 or from 1.30.0 up to, but not including, 1.31.1 should check their generated clients.