Blue OceanApplication · Jenkins
CVE-2022-30952
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 · uneditedJenkins Pipeline SCM API for Blue Ocean Plugin 1.25.3 and earlier allows attackers with Job/Configure permission to access credentials with attacker-specified IDs stored in the private per-user credentials stores of any attacker-specified user in Jenkins.
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 confidenceThe Jenkins Pipeline SCM API for Blue Ocean Plugin versions 1.25.3 and earlier contains an authorization flaw allowing any user with Job/Configure permission to access arbitrary credentials stored in other users' private credential stores by specifying the target user ID and credential ID.
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
Blue OceanApplication
<= 1.25.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Blue Ocean plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Blue Ocean' in the filter, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i blueoceanAffected if Blue Ocean plugin is not listed in installed plugins, then the environment is not affected by this specific vulnerability.
-
Determine the installed Blue Ocean versionIn the Manage Plugins > Installed page, locate the Blue Ocean plugin and note the 'Version' column value. Alternatively, check the plugin's manifest file at $JENKINS_HOME/plugins/blueocean/META-INF/MANIFEST.MF for the Plugin-Version attribute.Affected if The version cannot be determined or the plugin metadata is missing, treat it as potentially vulnerable.
-
Compare installed version against affected rangeCompare the installed version number to 1.25.3. For version strings like '1.25.3', '1.25.3.1', or '1.25.2', check if the version is less than or equal to 1.25.3.Affected if The installed Blue Ocean version is 1.25.3 or any earlier version (e.g., 1.25.2, 1.25.1, 1.25.0), indicating the environment contains the vulnerable plugin.
-
Verify Job/Configure permission assignmentsReview Jenkins matrix-based security or project-based matrix authorization strategy at Manage Jenkins > Configure Global Security. Check which users or groups are granted the 'Job/Configure' permission, especially on jobs where they should not have credential configuration access.Affected if Users or groups have Job/Configure permission and the Blue Ocean plugin version is <= 1.25.3, then those users could potentially exploit this authorization flaw to access credentials outside their authorized scope.
The environment is affected if the Blue Ocean plugin is installed with version 1.25.3 or earlier AND users with Job/Configure permission exist who should not have access to other users' credentials.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade the Jenkins Pipeline SCM API for Blue Ocean Plugin to version 1.25.4 or later. Review credential usage and audit accessed credentials for any unauthorized access during the vulnerable period.
Fix this in Blue Ocean
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-30952 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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