What is CVE-2017-12097?

CVE-2017-12097 is a medium-severity cross-site scripting (XSS) vulnerability in delayed_job_web (rubygems), affecting versions >= 1.2.9, < 1.4.2. It is fixed in 1.4.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2017-12097?

CVE-2017-12097 has a CVSS score of 6.1 (Medium). 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 delayed_job_web are affected by CVE-2017-12097?

delayed_job_web (rubygems) versions >= 1.2.9, < 1.4.2 is affected.

Is there a fix for CVE-2017-12097?

Yes. CVE-2017-12097 is fixed in 1.4.2. Upgrade to this version or later.

Is CVE-2017-12097 exploitable, and should I be worried?

Whether CVE-2017-12097 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-2017-12097 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-2017-12097 in delayed_job_web

Q: How severe is CVE-2017-12097?

CVE-2017-12097 has a CVSS score of 6.1 (Medium). 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 delayed_job_web are affected by CVE-2017-12097?

delayed_job_web (rubygems) versions >= 1.2.9, < 1.4.2 is affected.

Q: Is there a fix for CVE-2017-12097?

Yes. CVE-2017-12097 is fixed in 1.4.2. Upgrade to this version or later.

Q: Is CVE-2017-12097 exploitable, and should I be worried?

Whether CVE-2017-12097 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-2017-12097 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-2017-12097?

Upgrade delayed_job_web to 1.4.2 or later.

Summary

delayedjobweb Cross-site Scripting vulnerability

An exploitable cross site scripting (XSS) vulnerability exists in the filter functionality of the delayed_job_web rails gem versions 1.2.9 before 1.4.2. A specially crafted URL can cause an XSS flaw resulting in an attacker being able to execute arbitrary javascript on the victim's browser. An attacker can phish an authenticated user to trigger this vulnerability.

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-2017-12097 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no 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.4.2); upgrading removes the vulnerable code path.

Affected versions

delayed_job_web (>= 1.2.9, < 1.4.2)

Security releases

delayed_job_web → 1.4.2 (rubygems)

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 delayed_job_web to 1.4.2 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-2017-12097? CVE-2017-12097 is a medium-severity cross-site scripting (XSS) vulnerability in delayed_job_web (rubygems), affecting versions >= 1.2.9, < 1.4.2. It is fixed in 1.4.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2017-12097? CVE-2017-12097 has a CVSS score of 6.1 (Medium). 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 delayed_job_web are affected by CVE-2017-12097? delayed_job_web (rubygems) versions >= 1.2.9, < 1.4.2 is affected.
Is there a fix for CVE-2017-12097? Yes. CVE-2017-12097 is fixed in 1.4.2. Upgrade to this version or later.
Is CVE-2017-12097 exploitable, and should I be worried? Whether CVE-2017-12097 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-2017-12097 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-2017-12097? Upgrade delayed_job_web to 1.4.2 or later.