dbcve.org
Sauce OndemandApplication · Jenkins

CVE-2022-34197

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 1.204 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 Sauce OnDemand Plugin 1.204 and earlier does not escape the name and description of Sauce Labs Browsers parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

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 Sauce OnDemand Plugin versions 1.204 and earlier fails to properly escape the name and description fields of Sauce Labs Browser parameters when rendering them in the UI. This allows an attacker with Item/Configure permission to inject malicious JavaScript code that executes in the browsers of other users viewing those parameters—classified as a stored (persistent) XSS vulnerability.

MitigationUpgrade the Sauce OnDemand plugin to version 1.205 or later which addresses the escaping issue. Until then, restrict Item/Configure permission to trusted users only and review existing job configurations for suspicious parameter values.

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
Sauce OndemandApplication
Affected:<= 1.204

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 if Sauce OnDemand plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Sauce OnDemand' or 'sauce-ondemand' in the list of installed plugins. Note the version number displayed.
    Affected if The plugin is installed and its version is 1.204 or earlier.
  2. Identify jobs using Sauce Labs Browser parameters
    Navigate to Manage Jenkins > Script Console and run: Jenkins.instance.allItems.each { if (it.class.canonicalName == 'hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper') { println it.fullName } } to list jobs using the Sauce OnDemand plugin.
    Affected if Any jobs are listed that use the Sauce OnDemand plugin.
  3. Inspect Sauce Labs Browser parameter names and descriptions for malicious script content
    For each identified job, go to Job > Configure and review any 'Sauce Labs Browser' parameters added under the Build Environment section. Check the 'Browser' and 'Browser Version' name and description fields for suspicious content such as <script>, javascript:, onload, onerror, or other HTML/JS patterns.
    Affected if Any parameter name or description field contains HTML script tags, JavaScript event handlers, or other code that could execute in a browser.
  4. Review user permissions for job configuration access
    Navigate to the affected jobs and check who has Item/Configure permission via Matrix Authorization Strategy or Project-based Matrix Authorization Strategy in the job configuration or global security settings.
    Affected if Users who are not fully trusted have Item/Configure permission on jobs that use Sauce Labs Browser parameters.

A user is affected if the Sauce OnDemand plugin version 1.204 or earlier is installed AND there are jobs configured with Sauce Labs Browser parameters containing unsanitized content in the name or description fields.

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.204
Interim mitigation

Upgrade the Sauce OnDemand plugin to version 1.205 or later which addresses the escaping issue. Until then, restrict Item/Configure permission to trusted users only and review existing job configurations for suspicious parameter values.

Recommended fix Moderate confidence

Sauce OnDemand plugin version > 1.204 (check Jenkins plugin repository for latest available version)

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Select the 'Installed' tab
  3. 3. Locate the Sauce OnDemand plugin in the list
  4. 4. If an update is available, select the plugin and click 'Update'
  5. 5. After updating, restart Jenkins or wait for the plugin to reload
  6. 6. Verify the plugin version is updated to confirm the fix was applied

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

Fix this in Sauce Ondemand 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-34197 — 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-34197 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