dbcve.org
Wmi Windows AgentsApplication · Jenkins

CVE-2022-30951

HIGH · 8.8 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to 1.8.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Jenkins WMI Windows Agents Plugin 1.8 and earlier includes the Windows Remote Command library does not implement access control, potentially allowing users to start processes even if they're not allowed to log in.

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

The Jenkins WMI Windows Agents Plugin version 1.8 and earlier includes a Windows Remote Command library that fails to implement access control checks. This authorization flaw allows authenticated Jenkins users who should not have login permissions to nonetheless execute arbitrary processes on Windows agent nodes through the WMI protocol.

MitigationUpgrade the WMI Windows Agents Plugin to version 1.9 or later which implements proper access control for the Windows Remote Command library. If upgrading is not immediately possible, restrict user permissions and review agent access policies.

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
Wmi Windows AgentsApplication
Affected:< 1.8.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 if WMI Windows Agents plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'WMI Windows Agents' or 'wmi windows agents' in the plugin list. Note the installed version if present.
    Affected if The plugin is listed with version 1.8 or earlier, or if no version is shown but the plugin name matches 'WMI Windows Agents' or 'WMIAgent'.
  2. Confirm the exact plugin version
    In the Installed plugins list, locate the 'WMI Windows Agents' entry and read the Version column. If using the Jenkins CLI, run: java -jar jenkins-cli.jar list-plugins 2>/dev/null | grep -i wmi
    Affected if The version shown is 1.8, 1.8.0, or any version lower than 1.8.1.
  3. Check if Windows agents are configured using WMI
    Navigate to Manage Jenkins > Manage Nodes > [node name]. Review the Launch method configuration. Look for launchers that reference WMI, WMI Windows Agents, or Windows Remote Management.
    Affected if Any Windows agent nodes are configured with a WMI-based launcher, especially if the launcher is provided by the WMI Windows Agents plugin.
  4. Review user permissions for agent-related operations
    Navigate to Manage Jenkins > Manage and Assign Roles > Manage Roles. Examine the Overall, Credentials, and Agent permissions assigned to each role. Specifically check if any role grants 'Connect agents' or 'Configure agents' to users who should not have login or agent access permissions.
    Affected if There exist users or roles that have agent connection or configuration permissions but should NOT have general login or full agent access based on your security policy.

You are affected if the WMI Windows Agents plugin version is 1.8 or earlier, Windows agents are configured using WMI launchers, and users with limited permissions can access agent configuration or connection features.

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 1.8.1 or later
Fixed in 1.8.1
Interim mitigation

Upgrade the WMI Windows Agents Plugin to version 1.9 or later which implements proper access control for the Windows Remote Command library. If upgrading is not immediately possible, restrict user permissions and review agent access policies.

Recommended fix High confidence

1.8.1

  1. Back up your Jenkins configuration and plugins directory before making changes
  2. Navigate to Jenkins Dashboard > Manage Jenkins > Manage Plugins
  3. Go to the 'Available' tab and search for 'WMI Windows Agents'
  4. Update the WMI Windows Agents plugin to version 1.8.1 or later
  5. Restart Jenkins to ensure the new plugin version is fully loaded
  6. Verify the update was successful by checking the installed plugins page
  7. Test that access controls are properly enforced by confirming users cannot start processes they are not authorized to run

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

Fix this in Wmi Windows Agents 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-2022-30951 — 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-2022-30951 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