Alerts This Week
Warning Icon 1 637
Alerts This Week
Warning Icon 1 637

Gentoo: GLSA-201309-07 High: libotr Code Execution Risk

gentoo
Calendar Grey September 15, 2013
Dist Gentoo Esm H88
Keep updated on GLSA 202209-12 regarding the critical vulnerability in Gentoo's libxyz memory leak with significant threat potential.
A buffer overflow vulnerability in libotr could allow a remote attacker to execute arbitrary code or cause a Denial of Service condition.

Summary

Multiple heap-based buffer overflows are present in the Base64 decoder of libotr.

Resolution

All libotr users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=net-libs/libotr-3.2.1"

References

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

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201309-07
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: High
Title: libotr: Arbitrary code execution
Date: September 15, 2013
Bugs: #430486
ID: 201309-07

Synopsis

A buffer overflow vulnerability in libotr could allow a remote attacker to execute arbitrary code or cause a Denial of Service condition.

Background

libotr is a portable off-the-record messaging library.

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 net-libs/libotr < 3.2.1 >= 3.2.1

Impact

===== A remote attacker could send a specially crafted OTR message, resulting in arbitrary code execution with the privileges of the process or a Denial of Service condition.

Workaround

There is no known workaround at this time.

Related News

Your message here