Insufficiently Protected Credentials in Jenkins Pipeline SCM API for Blue Ocean Plugin

Exploitation

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

CVSS

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

EPSS

• CVE-2022-30952: 1.02% estimated exploitation activity in the next 30 days; percentile 63.55 (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.

When pipelines are created using the pipeline creation wizard in Blue Ocean, the credentials used are stored in the per-user credentials store of the user creating the pipeline. To allow pipelines to use this credential to scan repositories and checkout from SCM, the Blue Ocean Credentials Provider allows pipelines to access a specific credential from the per-user credentials store in Pipeline SCM API for Blue Ocean Plugin 1.25.3 and earlier. As a result, attackers with Job/Configure permission can rewrite job configurations in a way that lets them access and capture any attacker-specified credential from any user’s private credentials store. Pipeline SCM API for Blue Ocean Plugin 1.25.4 deprecates the Blue Ocean Credentials Provider and disables it by default. As a result, all jobs initially set up using the Blue Ocean pipeline creation wizard and configured to use the credential specified at that time will no longer be able to access the credential, resulting in failures to scan…

Published by the source

18 May 2022, 00:00 UTC

Last modified by the source

15 Dec 2023, 09:39 UTC

Source last checked

26 Oct 2026, 16:21 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g74w-93cp-5p3p

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

# Patch Next advisory brief: CVE-2022-30952

Advisory: Insufficiently Protected Credentials in Jenkins Pipeline SCM API for Blue Ocean Plugin
IDs: CVE-2022-30952, GHSA-g74w-93cp-5p3p
Record: https://patchnext.com/advisories/cve-2022-30952 (revision 1, source checked 26 Oct 2026, 16:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.jenkins.blueocean:blueocean-pipeline-scm-api 1.25.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.jenkins.blueocean:blueocean-pipeline-scm-api: affected < 1.25.4; fixed in 1.25.4

## Suggested inspection (read-only)
- Maven io.jenkins.blueocean:blueocean-pipeline-scm-api: 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 io.jenkins.blueocean:blueocean-pipeline-scm-api.
- 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-g74w-93cp-5p3p (GitHub-reviewed advisory GHSA-g74w-93cp-5p3p lists affected ranges: Maven io.jenkins.blueocean:blueocean-pipeline-scm-api >=0 <1.25.4)

Commands are suggestions: review each one before running it.