vulnerability / NVI-00014986 / Revision 1
Microsoft Kiota: Generation-time SSRF + remote/local file inclusion via unrestricted $ref
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.
7.1 high
GitHub source severity; exploitability and local consequence require separate evidence.
As of · GitHub Advisory Database
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 Microsoft Kiota resolved OpenAPI `$ref`s by fetching remote `http(s)` URLs and reading local files (including absolute / out-of-tree paths), inlining the referenced schema into the generated client. Running `kiota generate` on a spec whose `$ref` pointed at an attacker/internal URL or an arbitrary local file yielded SSRF, remote file inclusion, and local file inclusion. Verified on **1.32.3 / 1.32.4**. ### Details - `$ref: http://attacker/internal-evil.json#/...` → build host fetches the URL (SSRF) and inlines the remote schema (RFI); confirmed property `REMOTE_KIOTA_PROP` in the generated client. - `$ref: /abs/path.json#/...` or `../../secret.json#/...` → Kiota reads the out-of-tree local file and inlines its schema (LFI); confirmed `Leaked` schema in the generated client. Resolution is transitive across nesting levels. Kiota **escapes** its output sinks (comments/strings/identifiers), so attacker-controlled remote/local content cannot break out into code — no RCE. The chain stops at SSRF + RFI + LFI. ### Impact Build-time SSRF (CWE-918) from the developer or CI host, disclosure of arbitrary local files (CWE-22), and inclusion of untrusted remote content (CW
Microsoft.OpenApi.Kiota.Builder
source listed>= 1.30.0, < 1.32.5
## Summary Microsoft Kiota resolved OpenAPI `$ref`s by fetching remote `http(s)` URLs and reading local files (including absolute / out-of-tree paths), inlining the referenced schema into the generated client. Running `kiota generate` on a spec whose `$ref` pointed at an attacker/internal URL or an arbitrary local file yielded SSRF, remote file inclusion, and local file inclusion. Verified on **1.32.3 / 1.32.4**. ### Details - `$ref: http://attacker/internal-evil.json#/...` → build host fetches the URL (SSRF) and inlines the remote schema (RFI); confirmed property `REMOTE_KIOTA_PROP` in the generated client. - `$ref: /abs/path.json#/...` or `../../secret.json#/...` → Kiota reads the out-of-tree local file and inlines its schema (LFI); confirmed `Leaked` schema in the generated client. Resolution is transitive across nesting levels. Kiota **escapes** its output sinks (comments/strings/identifiers), so attacker-controlled remote/local content cannot break out into code — no RCE. The chain stops at SSRF + RFI + LFI. ### Impact Build-time SSRF (CWE-918) from the developer or CI host, disclosure of arbitrary local files (CWE-22), and inclusion of untrusted remote content (CW
Microsoft.OpenApi.Kiota
source listed< 1.29.1
## Summary Microsoft Kiota resolved OpenAPI `$ref`s by fetching remote `http(s)` URLs and reading local files (including absolute / out-of-tree paths), inlining the referenced schema into the generated client. Running `kiota generate` on a spec whose `$ref` pointed at an attacker/internal URL or an arbitrary local file yielded SSRF, remote file inclusion, and local file inclusion. Verified on **1.32.3 / 1.32.4**. ### Details - `$ref: http://attacker/internal-evil.json#/...` → build host fetches the URL (SSRF) and inlines the remote schema (RFI); confirmed property `REMOTE_KIOTA_PROP` in the generated client. - `$ref: /abs/path.json#/...` or `../../secret.json#/...` → Kiota reads the out-of-tree local file and inlines its schema (LFI); confirmed `Leaked` schema in the generated client. Resolution is transitive across nesting levels. Kiota **escapes** its output sinks (comments/strings/identifiers), so attacker-controlled remote/local content cannot break out into code — no RCE. The chain stops at SSRF + RFI + LFI. ### Impact Build-time SSRF (CWE-918) from the developer or CI host, disclosure of arbitrary local files (CWE-22), and inclusion of untrusted remote content (CW
Microsoft.OpenApi.Kiota.Builder
source listed< 1.29.1
## Summary Microsoft Kiota resolved OpenAPI `$ref`s by fetching remote `http(s)` URLs and reading local files (including absolute / out-of-tree paths), inlining the referenced schema into the generated client. Running `kiota generate` on a spec whose `$ref` pointed at an attacker/internal URL or an arbitrary local file yielded SSRF, remote file inclusion, and local file inclusion. Verified on **1.32.3 / 1.32.4**. ### Details - `$ref: http://attacker/internal-evil.json#/...` → build host fetches the URL (SSRF) and inlines the remote schema (RFI); confirmed property `REMOTE_KIOTA_PROP` in the generated client. - `$ref: /abs/path.json#/...` or `../../secret.json#/...` → Kiota reads the out-of-tree local file and inlines its schema (LFI); confirmed `Leaked` schema in the generated client. Resolution is transitive across nesting levels. Kiota **escapes** its output sinks (comments/strings/identifiers), so attacker-controlled remote/local content cannot break out into code — no RCE. The chain stops at SSRF + RFI + LFI. ### Impact Build-time SSRF (CWE-918) from the developer or CI host, disclosure of arbitrary local files (CWE-22), and inclusion of untrusted remote content (CW
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-rg4h-fpcp-2qm8 ↗
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.