CVE-2022-29176 Unauthorized gem takeover for some gems on rubygems.org
Unauthorized users could replace specific Ruby gems, enabling supply chain attacks; RubyGems.org has patched the vulnerability.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-29176?
CVE-2022-29176 is a critical missing authorization vulnerability in rubygems.org, published on 5 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Rubygems is a package registry used to supply software for the Ruby language ecosystem. Due to a bug in the yank action, it was possible for any RubyGems.org user to remove and replace certain gems even if that user was not authorized to do so. To be vulnerable, a gem needed: one or more dashes in its name creation within 30 days OR no updates for over 100 days At present, we believe this vulnerability has not been exploited. RubyGems.org sends an email to all gem owners when a gem version is published or yanked. We have not received any support emails from gem owners indicating that their gem has been yanked without authorization. An audit of gem changes for the last 18 months did not find any examples of this vulnerability being used in a malicious way. A deeper audit for any possible use of this exploit is ongoing, and we will update this advisory once it is complete. Using Bundler in --frozen or --deployment mode in CI and during deploys, as the Bundler team has always recommended, will guarantee that your application does not silently switch to versions created using this exploit. To audit your application history for possible past exploits, review your Gemfile.lock and look for gems whose platform changed when the version number did not change. For example, gemname-3.1.2 updating to gemname-3.1.2-java could indicate a possible abuse of this vulnerability. RubyGems.org has been patched and is no longer vulnerable to this issue as of the 5th of May 2022.
Which versions are affected by CVE-2022-29176?
It affects 1 product.
Products include Rubygems Rubygems.org.
How do I fix CVE-2022-29176?
No fix has been published for CVE-2022-29176 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2022-29176 being exploited?
There is no known exploitation of CVE-2022-29176 in the wild and no public exploit code.