How severe is GHSA-73rf-6mrf-759q?

No CVSS score has been assigned to GHSA-73rf-6mrf-759q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-73rf-6mrf-759q?

GHSA-73rf-6mrf-759q affects the following packages: devise (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-73rf-6mrf-759q?

Update devise to 4.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-73rf-6mrf-759q is resolved across your whole dependency graph.

How do I detect GHSA-73rf-6mrf-759q in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for devise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-73rf-6mrf-759q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-73rf-6mrf-759q?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-73rf-6mrf-759q can be triaged on real exposure rather than presence alone.

Is GHSA-73rf-6mrf-759q actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-73rf-6mrf-759q, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-73rf-6mrf-759q?

GHSA-73rf-6mrf-759q has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-73rf-6mrf-759q?

GHSA-73rf-6mrf-759q is classified as CWE-367 (CWE-367), CWE-307 (CWE-307). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-73rf-6mrf-759q published, and has it been updated?

GHSA-73rf-6mrf-759q was published on March 19, 2019 and was last updated on November 30, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

GHSA-73rf-6mrf-759q — devise

Fix: plataformatec/devise#4996

GHSA-73rf-6mrf-759q is a CWE-367 vulnerability in devise. 1 public exploit reference exists, so weaponization risk is real. A fix is available for devise — see the affected versions and patch details below.

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

Also known asCVE-2019-5421

Published

Mar 19, 2019

Updated

Nov 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

💎devise

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Plataformatec Devise version 4.5.0 and earlier, using the lockable module contains a CWE-367 vulnerability in The Devise::Models::Lockable class, more specifically at the #increment_failed_attempts method. File location: lib/devise/models/lockable.rb that can result in Multiple concurrent requests can prevent an attacker from being blocked on brute force attacks. This attack appear to be exploitable via Network connectivity - brute force attacks. This vulnerability appears to have been fixed in 4.6.0 and later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`devise`	all versions	4.6.0`bundle update devise --conservative`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Plataformatec Devise version 4.5.0 and earlier, using the lockable modul…

github.comNVDOct 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for devise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update devise to 4.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-73rf-6mrf-759q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-73rf-6mrf-759q can be triaged on real exposure rather than presence alone.

Tailored to GHSA-73rf-6mrf-759q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Devise ruby gem before 4.6.0 when the `lockable` module is used is vulnerable to a time-of-check time-of-use (TOCTOU) race condition due to `increment_failed_attempts` within the `Devise::Models::Lockable` class not being concurrency safe.

O3 Security · Impact-Aware SCA

Is GHSA-73rf-6mrf-759q in your dependencies?

O3 Security finds GHSA-73rf-6mrf-759q across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works