What is CVE-2018-1000119?

CVE-2018-1000119 is a medium-severity security vulnerability in rack-protection (rubygems), affecting versions < 1.5.5. It is fixed in 1.5.5, 2.0.0.

How severe is CVE-2018-1000119?

CVE-2018-1000119 has a CVSS score of 5.9 (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 rack-protection are affected by CVE-2018-1000119?

rack-protection (rubygems) versions < 1.5.5 is affected.

Is there a fix for CVE-2018-1000119?

Yes. CVE-2018-1000119 is fixed in 1.5.5, 2.0.0. Upgrade to this version or later.

Is CVE-2018-1000119 exploitable, and should I be worried?

Whether CVE-2018-1000119 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-2018-1000119 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-2018-1000119 in rack-protection

Q: How severe is CVE-2018-1000119?

CVE-2018-1000119 has a CVSS score of 5.9 (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 rack-protection are affected by CVE-2018-1000119?

rack-protection (rubygems) versions < 1.5.5 is affected.

Q: Is there a fix for CVE-2018-1000119?

Yes. CVE-2018-1000119 is fixed in 1.5.5, 2.0.0. Upgrade to this version or later.

Q: Is CVE-2018-1000119 exploitable, and should I be worried?

Whether CVE-2018-1000119 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-2018-1000119 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-2018-1000119?

Upgrade: rack-protection to 1.5.5 or later, rack-protection to 2.0.0 or later.

Summary

rack-protection gem timing attack vulnerability when validating CSRF token

Sinatra rack-protection versions 1.5.4 and 2.0.0.rc3 and earlier contains a timing attack vulnerability in the CSRF token checking that can result in signatures can be exposed. This attack appear to be exploitable via network connectivity to the ruby application. This vulnerability appears to have been fixed in 1.5.5 and 2.0.0.

Impact

CVE-2018-1000119 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. 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.5.5, 2.0.0); upgrading removes the vulnerable code path.

Affected versions

rack-protection (< 1.5.5) rack-protection (>= 2.0.0.beta1, <= 2.0.0.rc3)

Security releases

rack-protection → 1.5.5 (rubygems) rack-protection → 2.0.0 (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 the following packages to resolve this vulnerability:

rack-protection to 1.5.5 or later; rack-protection to 2.0.0 or later

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

Frequently Asked Questions

What is CVE-2018-1000119? CVE-2018-1000119 is a medium-severity security vulnerability in rack-protection (rubygems), affecting versions < 1.5.5. It is fixed in 1.5.5, 2.0.0.
How severe is CVE-2018-1000119? CVE-2018-1000119 has a CVSS score of 5.9 (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 rack-protection are affected by CVE-2018-1000119? rack-protection (rubygems) versions < 1.5.5 is affected.
Is there a fix for CVE-2018-1000119? Yes. CVE-2018-1000119 is fixed in 1.5.5, 2.0.0. Upgrade to this version or later.
Is CVE-2018-1000119 exploitable, and should I be worried? Whether CVE-2018-1000119 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-2018-1000119 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-2018-1000119?
- Upgrade rack-protection to 1.5.5 or later
- Upgrade rack-protection to 2.0.0 or later