What is CVE-2022-34197?

CVE-2022-34197 is a high-severity cross-site scripting (XSS) vulnerability in org.jenkins-ci.plugins:sauce-ondemand (maven), affecting versions <= 1.204. It is fixed in 1.205. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2022-34197?

CVE-2022-34197 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.jenkins-ci.plugins:sauce-ondemand are affected by CVE-2022-34197?

org.jenkins-ci.plugins:sauce-ondemand (maven) versions <= 1.204 is affected.

Is there a fix for CVE-2022-34197?

Yes. CVE-2022-34197 is fixed in 1.205. Upgrade to this version or later.

Is CVE-2022-34197 exploitable, and should I be worried?

Whether CVE-2022-34197 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-34197 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2022-34197

Q: How severe is CVE-2022-34197?

CVE-2022-34197 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.jenkins-ci.plugins:sauce-ondemand are affected by CVE-2022-34197?

org.jenkins-ci.plugins:sauce-ondemand (maven) versions <= 1.204 is affected.

Q: Is there a fix for CVE-2022-34197?

Yes. CVE-2022-34197 is fixed in 1.205. Upgrade to this version or later.

Q: Is CVE-2022-34197 exploitable, and should I be worried?

Whether CVE-2022-34197 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-34197 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-34197?

Upgrade org.jenkins-ci.plugins:sauce-ondemand to 1.205 or later.

Summary

Cross-site Scripting in Jenkins Sauce OnDemand Plugin

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.

Exploitation of this vulnerability requires that parameters are listed on another page, like the "Build With Parameters" and "Parameters" pages provided by Jenkins (core), and that those pages are not hardened to prevent exploitation. Jenkins (core) has prevented exploitation of vulnerabilities of this kind on the "Build With Parameters" and "Parameters" pages since 2.44 and LTS 2.32.2 as part of the SECURITY-353 / CVE-2017-2601 fix. Additionally, several plugins have previously been updated to list parameters in a way that prevents exploitation by default, see SECURITY-2617 in the 2022-04-12 security advisory for a list.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-34197 has a CVSS score of 8.0 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.205); upgrading removes the vulnerable code path.

Affected versions

org.jenkins-ci.plugins:sauce-ondemand (<= 1.204)

Security releases

org.jenkins-ci.plugins:sauce-ondemand → 1.205 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade org.jenkins-ci.plugins:sauce-ondemand to 1.205 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-34197? CVE-2022-34197 is a high-severity cross-site scripting (XSS) vulnerability in org.jenkins-ci.plugins:sauce-ondemand (maven), affecting versions <= 1.204. It is fixed in 1.205. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2022-34197? CVE-2022-34197 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.jenkins-ci.plugins:sauce-ondemand are affected by CVE-2022-34197? org.jenkins-ci.plugins:sauce-ondemand (maven) versions <= 1.204 is affected.
Is there a fix for CVE-2022-34197? Yes. CVE-2022-34197 is fixed in 1.205. Upgrade to this version or later.
Is CVE-2022-34197 exploitable, and should I be worried? Whether CVE-2022-34197 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-34197 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-34197? Upgrade org.jenkins-ci.plugins:sauce-ondemand to 1.205 or later.