CriticalGHSA-rxq3-gm4p-5fj4CVE-2009-2422

rails vulnerable to improper authentication

Published 24 Oct 2017 · Updated 16 Feb 2024

Is your project on an affected rails?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

railsRubyGems
Affected
<2.3.3
Fixed in
2.3.3
Update to the fixed version for your release line, for example:bundle update --conservative rails # Gemfile: '>= 2.3.3'

Details

The example code for the digest authentication functionality (http_authentication.rb) in Ruby on Rails before 2.3.3 defines an authenticate_or_request_with_http_digest block that returns nil instead of false when the user does not exist, which allows context-dependent attackers to bypass authentication for applications that are derived from this example by sending an invalid username without a password.

Is GHSA-rxq3-gm4p-5fj4 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected rails, and gives you the command that fixes it.

More advisories for rails

  • MediumCVE-2024-26143Rails has possible XSS Vulnerability in Action Controller · 27 Feb 2024
  • HighCVE-2006-4112Rails Denial of Service vulnerability · 24 Oct 2017
  • HighCVE-2006-4111Ruby on Rails vulnerable to code injection · 24 Oct 2017
  • MediumCVE-2009-4214Moderate severity vulnerability that affects rails · 24 Oct 2017
  • MediumCVE-2007-5379Moderate severity vulnerability that affects rails · 24 Oct 2017
  • MediumCVE-2007-3227Moderate severity vulnerability that affects rails · 24 Oct 2017
All 11 advisories for rails

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.