dbcve.org
Blue OceanApplication · Jenkins

CVE-2022-30954

MEDIUM · 6.5 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to after 1.25.3 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
Jenkins Blue Ocean Plugin 1.25.3 and earlier does not perform a permission check in several HTTP endpoints, allowing attackers with Overall/Read permission to connect to an attacker-specified HTTP server.

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 Blue Ocean Plugin versions 1.25.3 and earlier lacks authorization checks on multiple HTTP endpoints. Any authenticated user with basic Overall/Read permission can cause the Jenkins server to connect to attacker-specified HTTP servers, enabling Server-Side Request Forgery (SSRF) attacks for internal network reconnaissance or data exfiltration.

MitigationUpgrade Blue Ocean Plugin to version 1.25.4 or later which implements proper permission checks on the affected HTTP endpoints. In the interim, restrict Overall/Read permission to only trusted users.

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
Affected:<= 1.25.3

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. Verify Blue Ocean plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins | grep -i 'blue ocean'
    Affected if Blue Ocean plugin appears in the installed plugins list
  2. Determine installed Blue Ocean version
    In Jenkins web UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate Blue Ocean in the list to view its version number, or check the plugin's manifest file (META-INF/MANIFEST.MF) in the plugin directory on the Jenkins controller
    Affected if Version is 1.25.3 or earlier
  3. Confirm plugin is active and endpoints are reachable
    Access the Blue Ocean web interface at /blue/ or verify the Blue Ocean REST API endpoints are accessible (e.g., GET requests to /blue/rest/...), or check that the Blue Ocean route is listed in Manage Jenkins > Configure Global Security > Authorization
    Affected if Blue Ocean plugin is active and responding to HTTP requests
  4. Verify users with Overall/Read permission exist
    Go to Manage Jenkins > Manage Users, or check the authorization matrix in Manage Jenkins > Configure Global Security to confirm the presence of users granted Overall/Read permission (this is the default permission granted to authenticated users in standard Jenkins setups)
    Affected if Any user account exists with Overall/Read permission, which is typical for authenticated user access

Your environment is affected if Blue Ocean plugin version 1.25.3 or earlier is installed, the plugin is active and accessible, and any user with Overall/Read permission exists in the system.

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 1.25.3
Interim mitigation

Upgrade Blue Ocean Plugin to version 1.25.4 or later which implements proper permission checks on the affected HTTP endpoints. In the interim, restrict Overall/Read permission to only trusted users.

Recommended fix Moderate confidence

Blue Ocean plugin version 1.25.4 or later

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Locate the 'Available' tab and search for 'Blue Ocean'
  3. If an update is available, select the Blue Ocean plugin and click 'Download now and install after restart'
  4. Alternatively, download the updated .hpi file from the Jenkins plugin repository and upload it via 'Advanced' > 'Upload Plugin'
  5. Restart Jenkins to apply the update
  6. Verify the Blue Ocean plugin version is updated to confirm the patch was applied

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

Fix this in Blue Ocean Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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