dbcve.org
Azure AgentApplication · Microsoft

CVE-2025-21199

MEDIUM · 6.7 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 2.0.9940.0 / 9.30 or later.
See remediation →
67/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper privilege management in Azure Agent Installer allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper privilege management in Azure Agent Installer enables a locally authorized attacker to escalate privileges. This appears to be a local privilege escalation vulnerability where the installer improperly handles privilege assignment, allowing an authenticated user to gain elevated (likely administrator or SYSTEM) privileges on the Windows system where the Azure Agent is installed.

MitigationApply the vendor patch for Azure Agent Installer when available. Until then, restrict physical and logical access to systems with Azure Agent Installer installations to authorized administrators only, and monitor for suspicious process execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Azure AgentApplication
Affected:< 2.0.9940.0< 9.30

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Azure Agent installation
    Check for the presence of Azure Agent by looking for azure-agent, vss_agent, or related executable files in typical installation directories such as C:\Program Files\Microsoft\Azure Agent or C:\Program Files (x86)\Microsoft\Azure Agent, or search for the process azagent.exe, AzureConnectedAgent.exe, or similar Azure agent processes running on the system.
    Affected if Azure Agent is found installed on the system.
  2. Determine installed Azure Agent version
    Right-click the Azure Agent executable (such as azagent.exe or AzureConnectedAgent.exe), select Properties, and navigate to the Details tab to view the File Version. Alternatively, open Command Prompt and run: where /r C:\ azagent.exe or where /r "C:\Program Files" azagent.exe to locate the executable, then run: "C:\path\to\azagent.exe" --version if supported, or inspect the file version property.
    Affected if The version shown is below 2.0.9940.0 or below 9.30.
  3. Verify Azure Agent service configuration
    Open Services (services.msc) and locate any Azure-related agent services such as Azure Agent, Azure Pipelines Agent, or Azure Connected Agent. Right-click the service, select Properties, and note the service name and the executable path it points to.
    Affected if An Azure Agent service is found running with an executable path matching an affected version.
  4. Check installer components and permissions
    Navigate to the Azure Agent installation directory (typically in Program Files or Program Files (x86)), locate installer-related executables or scripts (such as run.exe, bin\Installer\*.exe, or similar), right-click each, select Properties, and review the file version. Check if any installer components exist with versions that can be determined.
    Affected if Installer components are present and their version cannot be determined or matches the affected version range.

A system is affected if Azure Agent or its installer components are installed with a version below 2.0.9940.0 or below 9.30, allowing a locally authorized attacker to exploit improper privilege assignment in the installer to gain elevated privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.9940.0 / 9.30 or later
Fixed in 2.0.9940.09.30
Interim mitigation

Apply the vendor patch for Azure Agent Installer when available. Until then, restrict physical and logical access to systems with Azure Agent Installer installations to authorized administrators only, and monitor for suspicious process execution.

Recommended fix High confidence

Azure Agent version 2.0.9940.0 or 9.30 (or later)

  1. Identify the currently installed Azure Agent version using 'az agent version' or checking the installed package
  2. Upgrade Azure Agent to version 2.0.9940.0 or higher (or version 9.30 or higher depending on the agent branch)
  3. Verify the upgrade was successful by running 'az agent version' to confirm the new version
  4. Test that the Azure Agent functions normally after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Azure Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21199 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data