dbcve.org
Azure Vm AgentsApplication · Jenkins

CVE-2023-32989

HIGH · 8.8 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to after 852.v8d35f0960a_43 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A cross-site request forgery (CSRF) vulnerability in Jenkins Azure VM Agents Plugin 852.v8d35f0960a_43 and earlier allows attackers to connect to an attacker-specified Azure Cloud server using attacker-specified credentials IDs obtained through another method.

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 · high confidence

This is a CSRF vulnerability in the Jenkins Azure VM Agents Plugin versions 852.v8d35f0960a_43 and earlier. The flaw allows authenticated users to be tricked into unknowingly submitting requests that connect to an attacker-controlled Azure Cloud server using attacker-specified credential IDs that were obtained through a separate method.

MitigationUpgrade the Azure VM Agents Plugin to a patched version beyond 852.v8d35f0960a_43 that includes proper CSRF token validation on affected form submissions.

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 Vm AgentsApplication
Affected:<= 852.v8d35f0960a_43

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Azure VM Agents Plugin is installed
    Log into Jenkins and navigate to Manage Jenkins > Manage Plugins > Installed, or use the Jenkins script console: jenkins.model.Jenkins.instance.getPluginManager().getPlugin('azure-vm-agents')
    Affected if The plugin is not found or not installed means not affected
  2. Determine installed plugin version
    In Manage Plugins > Installed, find 'Azure VM Agents' and note the version column; or via script console: println jenkins.model.Jenkins.instance.getPluginManager().getPlugin('azure-vm-agents').getVersion()
    Affected if Version is 852.v8d35f0960a_43 or earlier indicates vulnerability is present
  3. Confirm Azure cloud configuration exists
    Navigate to Manage Jenkins > Manage Nodes and Clouds > Configure Clouds, or check if Azure VM Agents cloud configuration is present via Manage Jenkins > Configure System for Azure VM Agents sections
    Affected if If no Azure cloud configuration exists, the CSRF attack surface is not present; however, the vulnerable code still exists in the plugin regardless of configuration
  4. Verify credential binding for Azure plugin
    Check Manage Jenkins > Manage Credentials to see if any Azure credential IDs are defined; the CSRF exploits ability to trigger connections using attacker-specified credential IDs obtained separately
    Affected if If credentials exist and plugin version is vulnerable, the CSRF could be exploited to use those credentials

User is affected if the Azure VM Agents Plugin version is 852.v8d35f0960a_43 or earlier AND the plugin is installed, regardless of whether Azure cloud configurations are actively in use.

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 a release after 852.v8d35f0960a_43
Interim mitigation

Upgrade the Azure VM Agents Plugin to a patched version beyond 852.v8d35f0960a_43 that includes proper CSRF token validation on affected form submissions.

Recommended fix Moderate confidence

852.v8d35f0960a_44 or later

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Select the 'Updates' tab
  3. 3. Locate the 'Azure VM Agents' plugin in the list
  4. 4. Select the plugin and click 'Download now and install after restart'
  5. 5. Wait for the plugin to update
  6. 6. Restart Jenkins to complete the installation
  7. 7. Verify the updated version is 852.v8d35f0960a_44 or later in Manage Plugins > Installed

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

Fix this in Azure Vm Agents Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32989 — 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-2023-32989 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