CVE-2019-5421: devise Time-of-check Time-of-use Race Condition vulnerability

CVE-2019-5421 · Severity: info · Published 2019-03-19

devise Time-of-check Time-of-use Race Condition vulnerability

Technologies: devise (RubyGems). Vendors: RubyGems.

Quick answers

Is CVE-2019-5421 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-5421 being exploited in the wild.
How severe is CVE-2019-5421?
Informational severity, published 19 March 2019.
Which products and versions are affected?
devise (RubyGems) ECOSYSTEM:introduced=0,fixed=4.6.0.
Is there a fix for CVE-2019-5421?
Yes. devise (RubyGems): upgrade to 4.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-5421?
Check whether you run devise (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • devise (RubyGems): upgrade to 4.6.0 or later
    bundle update devise

Affected products

  • devise (RubyGems) ECOSYSTEM:introduced=0,fixed=4.6.0

Identifiers

  • CVE-2019-5421
  • GHSA-73rf-6mrf-759q

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.