MediumGHSA-228f-g3h7-3fj3CVE-2012-2125

RubyGems HTTPS to HTTP redirect

Published 17 May 2022 · Updated 2 Dec 2024

Is your project on an affected rubygems-update?

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

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

Details

RubyGems before 1.8.23 can redirect HTTPS connections to HTTP, which makes it easier for remote attackers to observe or modify a gem during installation via a man-in-the-middle attack.

Is GHSA-228f-g3h7-3fj3 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 rubygems-update, and gives you the command that fixes it.

More advisories for rubygems-update

  • MediumCVE-2012-2126RubyGems does not verify SSL certificate · 17 May 2022
  • MediumCVE-2013-4363RubyGems Regular Expression Denial of Service · 17 May 2022
  • MediumCVE-2015-4020RubyGems Improper Input Validation vulnerability · 17 May 2022
  • MediumCVE-2018-1000079RubyGems Path Traversal vulnerability · 14 May 2022
  • HighCVE-2015-3900RubyGems vulnerable to DNS hijack attack · 14 May 2022
  • MediumCVE-2013-4287RubyGems Regular Expression Denial of Service vulnerability · 14 May 2022
All 25 advisories for rubygems-update

References

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