CVE-2012-2126 RubyGems does not verify SSL certificate
RubyGems fails to verify SSL certificates, allowing attackers to inject malicious code into gems during installation via man-in-the-middle attacks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2012-2126?
CVE-2012-2126 is a medium-severity vulnerability in n/a, published on 1 Oct 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
RubyGems before 1.8.23 does not verify an SSL certificate, which allows remote attackers to modify a gem during installation via a man-in-the-middle attack.
Weakness: CWE-310
Which versions are affected by CVE-2012-2126?
2 open source packages ship an affected version, including rubygems-update. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
rubygems-update RubyGems | All versions | 1.8.23 |
rubygems-update RubyGems | All versions | 1.8.23 |
Products include Rubygems Rubygems.
How do I fix CVE-2012-2126?
Upgrade rubygems-update to 1.8.23 or later.
Is CVE-2012-2126 being exploited?
There is no known exploitation of CVE-2012-2126 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2022-36073 RubyGems allows creation of users with arbitrary unverified emails
- CVE-2018-1000074 RubyGems Deserialization of Untrusted Data vulnerability
- CVE-2018-1000073 RubyGems Link Following vulnerability
- CVE-2019-8320 RubyGems Delete directory using symlink when decompressing tar
- CVE-2012-2125 RubyGems HTTPS to HTTP redirect
Sources
Also known as DEBIAN-CVE-2012-2126, GHSA-5mgj-mvv8-46mw, UBUNTU-CVE-2012-2126.