Skip to content

GHSA-fcjw-8rhj-gwwc CVE-2019-16109

Authentication Bypass in Devise

Medium RubyGems
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
1.83%
Chance of exploitation in the next 30 days. Higher than 78.89% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
4.7.1
Upgrade devise to this version or later

Description

An issue was discovered in Plataformatec Devise before 4.7.1. It confirms accounts upon receiving a request with a blank confirmation_token, if a database record has a blank value in the confirmation_token column. (However, there is no scenario within Devise itself in which such database records would exist.)

Affected versions

RubyGems

PackageVulnerableFixed in
devise
< 4.7.1
4.7.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

devise RubyGems → 4.7.1

bundler
bundle update devise # Gemfile: gem "devise", ">= 4.7.1"

Severity breakdown

CVSS 3.1 5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-jp94-3292-c3xv
Devise has an Open Redirect via Unvalidated `request.referrer` in Timeoutable Session Timeout Handler
Medium Also affects devise
GHSA-57hq-95w6-v4fc
Devise has a confirmable "change email" race condition permits user to confirm email they have no access to
Medium Also affects devise
GHSA-746g-3gfp-hfhw
Devise Gem for Ruby Unauthorized Access Using "Remember Me" Cookie
High Also affects devise
GHSA-73rf-6mrf-759q
devise Time-of-check Time-of-use Race Condition vulnerability
Medium Also affects devise
GHSA-jxhw-mg8m-2pj8
Devise does not properly perform type conversion when performing database queries
Medium Also affects devise
GHSA-8g5g-mxqh-grgj
Vite: `server.fs.deny` bypassed with queries
Medium Same weakness, CWE-284
GHSA-rq7h-c2jc-7f22
Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine
Medium Same weakness, CWE-284
GHSA-pjr3-86v4-5p7w
Vikunja: Explicit lower-permission share on a sub-project is silently overridden by an inherited parent permission (broken access control / privilege-management regression in v2.6.0)
Medium Same weakness, CWE-284
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor