Buffer overflow in Jenkins WMI Windows Agents plugin

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2022-30950: 1.89% estimated exploitation activity in the next 30 days; percentile 79.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

WMI Windows Agents Plugin 1.8 and earlier includes the Windows Remote Command library. It provides a general-purpose remote command execution capability that Jenkins uses to check if Java is available, and if not, to install it. This library has a buffer overflow vulnerability that may allow users able to connect to a named pipe to execute commands on the Windows agent machine. Additionally, while the processes are started as the user who connects to the named pipe, no access control takes place, potentially allowing users to start processes even if they’re not allowed to log in. WMI Windows Agents Plugin 1.8.1 no longer includes the Windows Remote Command library. A Java runtime is expected to be available on agent machines and WMI Windows Agents Plugin 1.8.1 does not install a JDK automatically otherwise.

Published by the source

18 May 2022, 00:00 UTC

Last modified by the source

28 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 16:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xhw3-wmx2-76wf

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

# Patch Next advisory brief: CVE-2022-30950

Advisory: Buffer overflow in Jenkins WMI Windows Agents plugin
IDs: CVE-2022-30950, GHSA-xhw3-wmx2-76wf
Record: https://patchnext.com/advisories/cve-2022-30950 (revision 1, source checked 26 Oct 2026, 16:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins:windows-slaves 1.8.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:windows-slaves: affected < 1.8.1; fixed in 1.8.1

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:windows-slaves: check the installed version with your package manager.

## 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 org.jenkins-ci.plugins:windows-slaves.
- 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://github.com/advisories/GHSA-xhw3-wmx2-76wf (GitHub-reviewed advisory GHSA-xhw3-wmx2-76wf lists affected ranges: Maven org.jenkins-ci.plugins:windows-slaves >=0 <1.8.1)

Commands are suggestions: review each one before running it.