dbcve.org
Azure Vm AgentsApplication · Jenkins

CVE-2023-32990

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to after 852.v8d35f0960a_43 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 missing permission check in Jenkins Azure VM Agents Plugin 852.v8d35f0960a_43 and earlier allows attackers with Overall/Read permission 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 missing permission check vulnerability in Jenkins Azure VM Agents Plugin versions 852.v8d35f0960a_43 and earlier. Attackers with basic Overall/Read permission can bypass intended authorization to connect to attacker-specified Azure Cloud servers using credentials IDs they obtain through other means, effectively exploiting an authorization bypass in the plugin's cloud connection functionality.

MitigationUpgrade Jenkins Azure VM Agents Plugin to a version newer than 852.v8d35f0960a_43 to receive the patched version that includes proper permission checks before allowing cloud server connections with specified credentials.

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

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

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. Check Azure VM Agents plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, then search for 'Azure VM Agents' to locate the plugin and note its version number
    Affected if The installed version is 852.v8d35f0960a_43 or any version earlier than this (lower version numbers indicate vulnerability)
  2. Verify Azure cloud configuration exists
    Navigate to Manage Jenkins > Configure System and look for Azure VM Agents or Azure Cloud configuration sections, or check agent configurations for Azure VM agent templates
    Affected if Any Azure cloud configuration with configured credentials is present in Jenkins system configuration
  3. Confirm user access levels
    Navigate to Manage Jenkins > Manage Users and check which users or groups have Overall/Read permission, or review authorization matrix settings under Manage Jenkins > Configure Global Security
    Affected if There are users granted Overall/Read permission (which is the default permission level that enables the bypass)

You are affected if the Azure VM Agents plugin version is 852.v8d35f0960a_43 or earlier AND your Jenkins instance has Azure cloud configurations with stored credentials AND any user account has Overall/Read permission.

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 Jenkins Azure VM Agents Plugin to a version newer than 852.v8d35f0960a_43 to receive the patched version that includes proper permission checks before allowing cloud server connections with specified credentials.

Recommended fix Moderate confidence

Latest version after 852.v8d35f0960a_43 (check Jenkins plugin repository for current secure release)

  1. 1. Navigate to the Jenkins plugin manager or the Jenkins Azure VM Agents plugin page
  2. 2. Check for available updates to the Azure VM Agents plugin
  3. 3. Upgrade the plugin to the latest available version that includes the security fix
  4. 4. Restart Jenkins if required to apply the update
  5. 5. Verify the plugin is updated and functioning correctly
Caveat Review release notes for any configuration or compatibility changes before upgrading

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
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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