Bug 822226 (CVE-2012-2369) - CVE-2012-2369 pidgin-otr: Format string security flaw in pidgin-otr
Summary: CVE-2012-2369 pidgin-otr: Format string security flaw in pidgin-otr
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2012-2369
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-16 17:33 UTC by Kurt Seifried
Modified: 2019-09-29 12:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-19 14:02:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Kurt Seifried 2012-05-16 17:33:30 UTC
Ian Goldberg iang.ca reports:

www.openwall.com/lists/oss-security/2012/05/16/2

Off-the-Record Messaging (OTR) Security Advisory 2012-01

Format string security flaw in pidgin-otr

Versions 3.2.0 and earlier of the pidgin-otr plugin contain a format
string security flaw.  This flaw could potentially be exploited by
a remote attacker to cause arbitrary code to be executed on the user's
machine.

The flaw is in pidgin-otr, not in libotr.  Other applications which use
libotr are not affected.

CVE-2012-2369 has been assigned to this issue.

The recommended course of action is to upgrade pidgin-otr to version
3.2.1 immediately.  The new version can be obtained here:

Source code:
    http://otr.cypherpunks.ca/pidgin-otr-3.2.1.tar.gz
gpg signature:
    http://otr.cypherpunks.ca/pidgin-otr-3.2.1.tar.gz.asc

git repository:
    git://otr.git.sourceforge.net/gitroot/otr/pidgin-otr (branch 3.2_dev)

Version 4.0.0 (soon to be released) does not suffer from this flaw.

Linux and *BSD vendors and package maintainers have been notified, and
updated packages should be available from them.

Comment 1 Paul Wouters 2012-06-15 17:53:55 UTC
these are all already in the updates repositories for EL6, F16 and F17


Note You need to log in before you can comment on or make changes to this bug.