Dashboard ViewApplication · Jenkins

CVE-2022-27197

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-15
Fix available
A fix is available. Upgrade to 2.18.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Dashboard View Plugin 2.18 and earlier does not perform URL validation for the Iframe Portlet's Iframe source URL, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure views.

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 Dashboard View Plugin versions 2.18 and earlier contains a stored cross-site scripting (XSS) vulnerability in the Iframe Portlet feature. The plugin fails to validate the iframe source URL parameter, allowing authenticated users with view configuration privileges to inject malicious JavaScript code that executes when other users view the dashboard.

MitigationUpgrade the Jenkins Dashboard View Plugin to version 2.18.1 or later, which includes proper URL validation for the Iframe Portlet source URL field.

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
Dashboard ViewApplication
Affected:< 2.18.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Check installed Jenkins Dashboard View Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, locate 'Dashboard View' plugin, and note the version number
    Affected if The installed version is 2.18 or earlier (below 2.18.1)
  2. Identify dashboards using Iframe Portlet
    Review each Dashboard View configuration and look for portlets or widgets named 'Iframe Portlet' or 'iframe'
    Affected if Any dashboard is configured with an Iframe Portlet widget
  3. Inspect Iframe Portlet source URL configuration
    For each Iframe Portlet found, view its configuration and examine the 'iframe source URL' or 'URL' parameter field
    Affected if The URL field contains unsanitized or potentially malicious content (e.g., javascript: URLs, unexpected domains, or suspicious patterns)
  4. Check for unauthorized or unexpected dashboards
    Review all Dashboard View configurations created by users with view configuration privileges, checking for unfamiliar Iframe Portlet entries
    Affected if There are Iframe Portlet configurations you did not create or that contain suspicious URLs

You are affected if the Dashboard View Plugin is installed at version 2.18 or earlier AND any dashboard contains an Iframe Portlet with a potentially malicious or unsanitized URL in the source field.

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 2.18.1 or later
Fixed in 2.18.1
Interim mitigation

Upgrade the Jenkins Dashboard View Plugin to version 2.18.1 or later, which includes proper URL validation for the Iframe Portlet source URL field.

Recommended fix High confidence

Dashboard View plugin version 2.18.1 or later

  1. 1. In the Jenkins web UI, navigate to 'Manage Jenkins' > 'Manage Plugins'
  2. 2. Click on the 'Installed' tab to view installed plugins
  3. 3. Locate the 'Dashboard View' plugin in the list
  4. 4. If an update is available, check the plugin row and click 'Update'
  5. 5. After the update completes, restart Jenkins (or wait for the pending restart if using Jenkins 2.214+ with safe restart enabled)
  6. 6. Verify the plugin version is 2.18.1 or later under 'Manage Jenkins' > 'Manage Plugins' > 'Installed'

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

Fix this in Dashboard View Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27197 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