Authenticated code execution via unvalidated credential arguments
Published Oct 10, 2023 · Updated Apr 14, 2025
Command injection in Microsoft Azure Identity SDK for .NET before 1.10.2 allows remote authenticated users to execute arbitrary code. AzureCliCredential, AzureDeveloperCliCredential, and AzurePowerShellCredential build subprocess arguments from tenant identifiers or scopes without first validating those values. Exploitation requires an application to pass attacker-controlled credential parameters, and injected commands run with that application's privileges.
Summary
What happened
Command injection in Microsoft Azure Identity SDK for .NET before 1.10.2 allows remote authenticated users to execute arbitrary code. AzureCliCredential, AzureDeveloperCliCredential, and AzurePowerShellCredential build subprocess arguments from tenant identifiers or scopes without first validating those values. Exploitation requires an application to pass attacker-controlled credential parameters, and injected commands run with that application's privileges.
The record
- CVE
- CVE-2023-36414
- Published
- Oct 10, 2023
- Updated
- Apr 14, 2025
- Vendor
- Microsoft
- Product
- Azure Identity SDK for .NET
- Classifications
- CWE-77, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 10, 2023CVE publishedPublication date reported by the CVE source.
- Apr 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <1.10.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo