dbcve.org
Embeddable Build StatusApplication · Jenkins

CVE-2022-34179

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 allows specifying a `style` query parameter that is used to choose a different SVG image style without restricting possible values, resulting in a relative path traversal vulnerability that allows attackers without Overall/Read permission to specify paths to other SVG images on the Jenkins controller file system.

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 a path traversal vulnerability in its `style` query parameter handling. The plugin does not validate or restrict the style parameter value, allowing attackers to use relative path traversal sequences (e.g., ../../../) to access arbitrary SVG files on the Jenkins controller file system, even without Overall/Read permissions.

MitigationUpdate the Embeddable Build Status Plugin to a patched version that properly validates the style parameter against an allowlist of permitted values, or temporarily disable the plugin if an update is not immediately available.

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 Embeddable Build Status Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Embeddable Build Status', or inspect the file system at $JENKINS_HOME/plugins/ for a directory named 'embeddable-build-status'
    Affected if The plugin directory exists or is listed in the installed plugins
  2. Determine installed plugin version
    In the Manage Plugins > Installed tab, locate the Embeddable Build Status Plugin and note the Version column; alternatively, check the plugin's manifest.mf or plugin.xml file inside the plugin directory
    Affected if The version is 2.0.3 or lower
  3. Confirm plugin endpoint accessibility
    Attempt to access the build status endpoint (typically at /embeddable-build-status/buildStatus or /buildStatus/icon) with a style parameter, for example: curl -I 'http://JENKINS_HOST/embeddable-build-status/buildStatus/icon?style=../../../some/path'
    Affected if The endpoint responds and accepts the style parameter without authentication failure
  4. Check for exposed build status on unauthenticated paths
    Review Jenkins configuration for any views or URLs that expose the Embeddable Build Status endpoint to unauthenticated or anonymous users, typically under Manage Jenkins > Configure Global Security > Access Control
    Affected if Anonymous or unauthenticated users can reach the plugin's build status URL

You are affected if the Embeddable Build Status Plugin is installed at version 2.0.3 or lower and its endpoint with the style parameter is accessible to unauthenticated users.

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

Update the Embeddable Build Status Plugin to a patched version that properly validates the style parameter against an allowlist of permitted values, or temporarily disable the plugin if an update is not immediately available.

Recommended fix High confidence

Embeddable Build Status Plugin version 2.0.4 or later

  1. Navigate to Jenkins dashboard > Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab and locate the 'Embeddable Build Status' plugin
  3. Check if the current version is 2.0.3 or earlier
  4. If vulnerable, select the plugin and click 'Update now' to fetch the latest version
  5. Alternatively, download the updated plugin from the Jenkins Update Center
  6. Restart Jenkins if required after the update
  7. Verify the plugin version has been updated to confirm the patch is applied

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

Fix this in Embeddable Build Status Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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