- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201309-07
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            https://security.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.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  net-libs/libotr              < 3.2.1                    >= 3.2.1

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

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.

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

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.

License
======
Copyright 2013 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/

Gentoo: GLSA-201309-07: libotr: Arbitrary code execution

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

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
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.

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