It was found that RubyGems did not verify SSL connections. This could lead to man-in-the-middle attacks. (CVE-2012-2126)

It was found that, when using RubyGems, the connection could be redirected from HTTPS to HTTP. This could lead to a user believing they are installing a gem via HTTPS, when the connection may have been silently downgraded to HTTP. (CVE-2012-2125)

It was discovered that the rubygems API validated version strings using an unsafe regular expression. An application making use of this API to process a version string from an untrusted source could be vulnerable to a denial of service attack through CPU exhaustion.
(CVE-2013-4287)

It was discovered that Ruby incorrectly allowed untainted strings to be modified in protective safe levels. An attacker could use this flaw to bypass intended access restrictions. (CVE-2011-1005)

John Firebaugh discovered that the RubyGems remote gem fetcher did not properly verify SSL certificates. A remote attacker could exploit this to perform a man in the middle attack to alter gem files being downloaded for installation. (CVE-2012-2126)

John Firebaugh discovered that the RubyGems remote gem fetcher allowed redirection from HTTPS to HTTP. A remote attacker could exploit this to perform a man in the middle attack to alter gem files being downloaded for installation. (CVE-2012-2125).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

From Red Hat Security Advisory 2013:1441 :

An updated rubygems package that fixes three security issues is now available for Red Hat Enterprise Linux 6.

The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

RubyGems is the Ruby standard for publishing and managing third-party libraries.

It was found that RubyGems did not verify SSL connections. This could lead to man-in-the-middle attacks. (CVE-2012-2126)

It was found that, when using RubyGems, the connection could be redirected from HTTPS to HTTP. This could lead to a user believing they are installing a gem via HTTPS, when the connection may have been silently downgraded to HTTP. (CVE-2012-2125)

It was discovered that the rubygems API validated version strings using an unsafe regular expression. An application making use of this API to process a version string from an untrusted source could be vulnerable to a denial of service attack through CPU exhaustion.
(CVE-2013-4287)

Red Hat would like to thank Rubygems upstream for reporting CVE-2013-4287. Upstream acknowledges Damir Sharipov as the original reporter.

All rubygems users are advised to upgrade to this updated package, which contains backported patches to correct these issues.

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.

With this new rubygems, HTTPS connection no longer redirects to HTTP.
Also now rubygems verify SSL connection.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Solaris system is missing necessary patches to address security updates :

  - 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. (CVE-2012-2125)

  - 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.
    (CVE-2012-2126)

An updated rubygems package that fixes two security issues is now available for Red Hat OpenShift Enterprise 1.2.2.

The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.

RubyGems is the Ruby standard for publishing and managing third-party libraries.

It was found that, when using RubyGems, the connection could be redirected from HTTPS to HTTP. This could lead to a user believing they are installing a gem via HTTPS, when the connection may have been silently downgraded to HTTP. (CVE-2012-2125)

It was found that RubyGems did not verify SSL connections. This could lead to man-in-the-middle attacks. (CVE-2012-2126)

All users of Red Hat OpenShift Enterprise 1.2.2 are advised to upgrade to this updated package, which corrects these issues.

John Firebaugh discovered that the RubyGems remote gem fetcher did not properly verify SSL certificates. A remote attacker could exploit this to perform a man in the middle attack to alter gem files being downloaded for installation. (CVE-2012-2126)

John Firebaugh discovered that the RubyGems remote gem fetcher allowed redirection from HTTPS to HTTP. A remote attacker could exploit this to perform a man in the middle attack to alter gem files being downloaded for installation. (CVE-2012-2125).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

An updated rubygems package that fixes three security issues is now available for Red Hat Enterprise Linux 6.

The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

RubyGems is the Ruby standard for publishing and managing third-party libraries.

It was found that RubyGems did not verify SSL connections. This could lead to man-in-the-middle attacks. (CVE-2012-2126)

It was found that, when using RubyGems, the connection could be redirected from HTTPS to HTTP. This could lead to a user believing they are installing a gem via HTTPS, when the connection may have been silently downgraded to HTTP. (CVE-2012-2125)

It was discovered that the rubygems API validated version strings using an unsafe regular expression. An application making use of this API to process a version string from an untrusted source could be vulnerable to a denial of service attack through CPU exhaustion.
(CVE-2013-4287)

Red Hat would like to thank Rubygems upstream for reporting CVE-2013-4287. Upstream acknowledges Damir Sharipov as the original reporter.

All rubygems users are advised to upgrade to this updated package, which contains backported patches to correct these issues.

Updated Grid component packages that fix multiple security issues are now available for Red Hat Enterprise MRG 2.4 for Red Hat Enterprise Linux 6.

The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

Red Hat Enterprise MRG (Messaging, Realtime, and Grid) is a next-generation IT infrastructure for enterprise computing. MRG offers increased performance, reliability, interoperability, and faster computing for enterprise customers.

MRG Grid provides high-throughput computing and enables enterprises to achieve higher peak computing capacity as well as improved infrastructure utilization by leveraging their existing technology to build high performance grids. MRG Grid provides a job-queueing mechanism, scheduling policy, and a priority scheme, as well as resource monitoring and resource management. Users submit their jobs to MRG Grid, where they are placed into a queue. MRG Grid then chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion.

It was found that, when using RubyGems, the connection could be redirected from HTTPS to HTTP. This could lead to a user believing they are installing a gem via HTTPS, when the connection may have been silently downgraded to HTTP. (CVE-2012-2125)

It was found that RubyGems did not verify SSL connections. This could lead to man-in-the-middle attacks. (CVE-2012-2126)

It was discovered that the rubygems API validated version strings using an unsafe regular expression. An application making use of this API to process a version string from an untrusted source could be vulnerable to a denial of service attack through CPU exhaustion.
(CVE-2013-4287)

A flaw was found in the way cumin enforced user roles, allowing an unprivileged cumin user to access a range of resources without having the appropriate role. A remote, authenticated attacker could use this flaw to access privileged information, and perform a variety of privileged operations. (CVE-2013-4404)

It was found that multiple forms in the cumin web interface did not protect against Cross-Site Request Forgery (CSRF) attacks. If a remote attacker could trick a user, who is logged into the cumin web interface, into visiting a specially crafted URL, the attacker could perform actions in the context of the logged in user. (CVE-2013-4405)

It was found that cumin did not properly escape input from the 'Max allowance' field in the 'Set limit' form of the cumin web interface. A remote attacker could use this flaw to perform cross-site scripting (XSS) attacks against victims by tricking them into visiting a specially crafted URL. (CVE-2013-4414)

A flaw was found in the way cumin parsed POST request data. A remote attacker could potentially use this flaw to perform SQL injection attacks on cumin's database. (CVE-2013-4461)

Red Hat would like to thank Rubygems upstream for reporting CVE-2013-4287. Upstream acknowledges Damir Sharipov as the original reporter of CVE-2013-4287. The CVE-2013-4404, CVE-2013-4405, CVE-2013-4414, and CVE-2013-4461 issues were discovered by Tomas Novacik of the Red Hat MRG Quality Engineering team.

All users of the Grid capabilities of Red Hat Enterprise MRG are advised to upgrade to these updated packages, which correct these issues.

New version 1.8.23 is released.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Redhat Enterprise Linux 6 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2013:1441 advisory.

    RubyGems is the Ruby standard for publishing and managing third-party     libraries.

    It was found that RubyGems did not verify SSL connections. This could lead     to man-in-the-middle attacks. (CVE-2012-2126)

    It was found that, when using RubyGems, the connection could be redirected     from HTTPS to HTTP. This could lead to a user believing they are installing     a gem via HTTPS, when the connection may have been silently downgraded to     HTTP. (CVE-2012-2125)

    It was discovered that the rubygems API validated version strings using an     unsafe regular expression. An application making use of this API to process     a version string from an untrusted source could be vulnerable to a denial     of service attack through CPU exhaustion. (CVE-2013-4287)

    Red Hat would like to thank Rubygems upstream for reporting CVE-2013-4287.
    Upstream acknowledges Damir Sharipov as the original reporter.

    All rubygems users are advised to upgrade to this updated package, which     contains backported patches to correct these issues.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
70491	Scientific Linux Security Update : rubygems on SL6.x (noarch) (20131017)	Nessus	Scientific Linux Local Security Checks	10/18/2013	1/14/2021	medium
62307	Ubuntu 12.04 LTS : ruby1.9.1 vulnerabilities (USN-1583-1)	Nessus	Ubuntu Local Security Checks	9/26/2012	9/19/2019	medium
70524	Oracle Linux 6 : rubygems (ELSA-2013-1441)	Nessus	Oracle Linux Local Security Checks	10/20/2013	1/14/2021	medium
69686	Amazon Linux AMI : rubygems (ALAS-2012-79)	Nessus	Amazon Linux Local Security Checks	9/4/2013	4/18/2018	medium
58935	Fedora 15 : rubygems-1.7.2-5.fc15 (2012-6414)	Nessus	Fedora Local Security Checks	5/1/2012	1/11/2021	medium
80759	Oracle Solaris Third-Party Patch Update : rubygems (cve_2012_2125_https_to)	Nessus	Solaris Local Security Checks	1/19/2015	1/14/2021	medium
58933	Fedora 16 : rubygems-1.8.11-3.fc16.1 (2012-6409)	Nessus	Fedora Local Security Checks	5/1/2012	1/11/2021	medium
119343	RHEL 6 : rubygems (RHSA-2013:1203)	Nessus	Red Hat Local Security Checks	12/4/2018	7/17/2024	medium
62306	Ubuntu 12.04 LTS : rubygems vulnerabilities (USN-1582-1)	Nessus	Ubuntu Local Security Checks	9/26/2012	9/19/2019	medium
70501	CentOS 6 : rubygems (CESA-2013:1441)	Nessus	CentOS Local Security Checks	10/20/2013	1/4/2021	medium
76671	RHEL 6 : MRG (RHSA-2013:1852)	Nessus	Red Hat Local Security Checks	7/22/2014	1/14/2021	high
58957	Fedora 17 : rubygems-1.8.23-20.fc17 (2012-6132)	Nessus	Fedora Local Security Checks	5/2/2012	1/11/2021	medium
70489	RHEL 6 : rubygems (RHSA-2013:1441)	Nessus	Red Hat Local Security Checks	10/18/2013	11/4/2024	medium

Detections

Analytics

Plugins Search

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

high

medium

medium