CVE-2022-29176 Information

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.

CVSS Vector

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

Reference

https://hackerone.com/bugs?subject=rubygems&report_id=1559856 https://github.com/rubygems/rubygems.org/security/advisories/GHSA-hccv-rwq6-vh79

Attack Complexity

HIGH

Privileges Required

LOW

User Interaction Required

LOW

Scope

NONE

Confidentiality Impact

UNCHANGED

Integrity Impact

HIGH

Availability Impact

HIGH

Base Score

HIGH

Base Severity

7.5