Overly broad permissions can turn one compromised account into a much larger security problem. Learn how to reduce unnecessary access, review privileges, and apply least privilege across modern Linux systems. Review Linux Privileges×

Alerts This Week
Warning Icon 1 461
Alerts This Week
Warning Icon 1 461

Gentoo: GLSA-201405-14 Normal: Ruby OpenID Security Advisory

gentoo
Calendar Grey May 17, 2014
Scroller Gentoo
Vulnerability in Ruby OpenID poses Denial of Service threat for Gentoo users, necessitating an update to safeguard against potential exploits.
A vulnerability in Ruby OpenID may lead to Denial of Service.

Summary

An XML entity parsing error has been discovered in Ruby OpenID.

Resolution

All Ruby OpenID users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-ruby/ruby-openid-2.2.2"

References

[ 1 ] CVE-2013-1812 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-1812

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201405-14
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: Ruby OpenID: Denial of Service
Date: May 17, 2014
Bugs: #460156
ID: 201405-14

Synopsis

A vulnerability in Ruby OpenID may lead to Denial of Service.

Background

Ruby OpenID is a robust library for verifying and serving OpenID identities.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-ruby/ruby-openid < 2.2.2 >= 2.2.2

Impact

===== A remote attacker could send a specially crafted XML file, possibly resulting in a Denial of Service condition.

Workaround

There is no known workaround at this time.