Kiota: Unsafe oauth_card_path references in Kiota-generated API plugin manifests
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.35.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Kiota is an OpenAPI based HTTP Client code generator. From 1.25.1 until 1.35.0, Kiota copies x-ai-capabilities.response_semantics.oauth_card_path from an attacker-controlled or compromised OpenAPI description into a generated API plugin manifest without validating that the value is a safe package-relative file reference. Parent-directory traversal, rooted paths, or absolute URIs can therefore reach a consuming host that resolves the reference, allowing the host to cross the intended plugin-package boundary or use an unintended authentication card. Kiota does not itself read a local file or execute code merely while generating the manifest, and impact requires downstream resolution of the unsafe reference. This issue is fixed in version 1.35.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- microsoft kiota
From 1.25.1 · fixed in 1.35.0
- microsoft Microsoft.OpenApi.Kiota
From 1.25.1 · fixed in 1.35.0
- microsoft Microsoft.OpenApi.Kiota.Builder
From 1.25.1 · fixed in 1.35.0
- Microsoft.OpenApi.KiotaNuGet
From 1.25.1 · fixed in 1.35.0
- Microsoft.OpenApi.Kiota.BuilderNuGet
From 1.25.1 · fixed in 1.35.0