HighGHSA-4wm8-fjv7-j774CVE-2019-8325

RubyGems Escape sequence injection in errors

Published 20 Jun 2019 · Updated 16 Feb 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 packages

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

Details

An issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::CommandManager#run calls alert_error without escaping, escape sequence injection is possible. (There are many ways to cause an error.)

Is GHSA-4wm8-fjv7-j774 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-2125RubyGems HTTPS to HTTP redirect · 17 May 2022
  • 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
All 25 advisories for rubygems-update

References

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