Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1amended

Improper Control of Generation of Code ('Code Injection') in Azure CLI

CVE-2022-39327GHSA-47xc-9rr2-q7p4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (azure-cli 2.40.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2022-39327: 4.17% estimated exploitation activity in the next 30 days; percentile 90.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Description In versions previous to 2.40.0, Azure CLI contains a vulnerability for potential code injection. Critical scenarios are where a hosting machine runs an Azure CLI command where parameter values have been provided by an external source. For example: Application X is a web application with a feature that allows users to create Secrets in an Azure KeyVault. Instead of constructing API calls based on user input, Application X uses Azure CLI commands to create the secrets. Application X has input fields presented to the user and the Azure CLI command parameter values are filled based on the user input fields. This input, when formed correctly, could potentially be run as system commands. Below is an example of the resulting Azure CLI command run on the web app's hosting machine. The above command could potentially run the whoami command on the hosting machine. Interactive, in-terminal use and automation/pipeline scenarios have not been identified as critical risk scenarios.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-47xc-9rr2-q7p4

  2. Revision 1 · created ·

    Published from osv record GHSA-47xc-9rr2-q7p4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-39327

Advisory: Improper Control of Generation of Code ('Code Injection') in Azure CLI
IDs: CVE-2022-39327, GHSA-47xc-9rr2-q7p4
Record: https://patchnext.com/advisories/cve-2022-39327 (revision 2, source checked 26 Oct 2026, 13:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: azure-cli 2.40.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI azure-cli: affected < 2.40.0; fixed in 2.40.0

## Suggested inspection (read-only)
- `python -m pip show azure-cli`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on azure-cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-47xc-9rr2-q7p4 (OSV record GHSA-47xc-9rr2-q7p4 lists affected ranges: PyPI azure-cli >=0 <2.40.0 (fixed))
- Verified: https://github.com/advisories/GHSA-47xc-9rr2-q7p4 (GitHub-reviewed advisory GHSA-47xc-9rr2-q7p4 lists affected ranges: PyPI azure-cli >=0 <2.40.0)

Commands are suggestions: review each one before running it.

Loading voting…