dbcve.org
Embeddable Build StatusApplication · Jenkins

CVE-2022-34180

HIGH · 7.5 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 2.0.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Embeddable Build Status Plugin 2.0.3 and earlier does not correctly perform the ViewStatus permission check in the HTTP endpoint it provides for "unprotected" status badge access, allowing attackers without any permissions to obtain the build status badge icon for any attacker-specified job and/or build.

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 Embeddable Build Status Plugin versions 2.0.3 and earlier contains an authorization bypass vulnerability where the ViewStatus permission check is incorrectly implemented in the HTTP endpoint for unprotected status badge access. This allows unauthenticated attackers to retrieve build status badge icons for any job and build by specifying them in the request, exposing build status information that should be protected.

MitigationUpgrade the Embeddable Build Status Plugin to version 2.0.4 or later, which contains the corrected permission check. If immediate upgrade is not possible, consider restricting access to the affected endpoint via network-level controls or temporarily disabling the plugin.

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
Embeddable Build StatusApplication
Affected:<= 2.0.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the Embeddable Build Status Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the $JENKINS_HOME/plugins/ directory for a folder named 'embeddable-build-status' or similar. Use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins to list installed plugins.
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In the Jenkins UI, find the Embeddable Build Status Plugin in the Installed tab and note the Version column. Alternatively, inspect the plugin's manifest file at $JENKINS_HOME/plugins/embeddable-build-status/META-INF/MANIFEST.MF for the Implementation-Version attribute.
    Affected if The version is 2.0.3 or earlier (e.g., 2.0.3, 2.0.2, 2.0.1, etc.)
  3. Confirm the plugin is active and enabled
    Check the plugin status in Manage Jenkins > Manage Plugins > Installed tab. A plugin can be installed but disabled. Also verify the plugin is not commented out in $JENKINS_HOME/jenkins.install.UpgradeWizard.state or other configuration files that might indicate it was intentionally disabled.
    Affected if The plugin shows as 'Enabled' or 'Active' in the Jenkins UI and responds to requests
  4. Test access to the vulnerable badge endpoint
    Attempt an unauthenticated HTTP request to a known build status badge path, such as: http://<JENKINS_HOST>/job/<JOB_NAME>/<BUILD_NUMBER>/badge/icon or http://<JENKINS_HOST>/buildStatus/icon?job=<JOB_NAME>. The exact path varies based on plugin configuration; check plugin documentation or inspect the plugin's web.xml for registered URL patterns.
    Affected if The request returns a badge icon (HTTP 200) without requiring authentication, indicating the authorization bypass is present

You are affected if the Embeddable Build Status Plugin version 2.0.3 or earlier is installed, enabled, and the status badge endpoint is accessible to unauthenticated users, allowing them to view build information for any job.

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.

From vendor data
Upgrade available Upgrade to a release after 2.0.3
Interim mitigation

Upgrade the Embeddable Build Status Plugin to version 2.0.4 or later, which contains the corrected permission check. If immediate upgrade is not possible, consider restricting access to the affected endpoint via network-level controls or temporarily disabling the plugin.

Fix this in Embeddable Build Status Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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