From: Alex Legler <a3li@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Cc: bugtraq@securityfocus.com, full-disclosure@lists.grok.org.uk,
security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 200905-07 ] Pidgin: Multiple vulnerabilities
Date: Mon, 25 May 2009 23:59:01 +0200 [thread overview]
Message-ID: <1243288741.7549.1.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 3579 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 200905-07
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: Pidgin: Multiple vulnerabilities
Date: May 25, 2009
Bugs: #270811
ID: 200905-07
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities in Pidgin might allow for the remote execution
of arbitrary code or a Denial of Service.
Background
==========
Pidgin (formerly Gaim) is an instant messaging client for a variety of
instant messaging protocols.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 net-im/pidgin < 2.5.6 >= 2.5.6
Description
===========
Multiple vulnerabilities have been discovered in Pidgin:
* Veracode reported a boundary error in the "XMPP SOCKS5 bytestream
server" when initiating an outgoing file transfer (CVE-2009-1373).
* Ka-Hing Cheung reported a heap corruption flaw in the QQ protocol
handler (CVE-2009-1374).
* A memory corruption flaw in "PurpleCircBuffer" was disclosed by
Josef Andrysek (CVE-2009-1375).
* The previous fix for CVE-2008-2927 contains a cast from uint64 to
size_t, possibly leading to an integer overflow (CVE-2009-1376, GLSA
200901-13).
Impact
======
A remote attacker could send specially crafted messages or files using
the MSN, XMPP or QQ protocols, possibly resulting in the execution of
arbitrary code with the privileges of the user running the application,
or a Denial of Service. NOTE: Successful exploitation might require the
victim's interaction.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Pidgin users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-im/pidgin-2.5.6"
References
==========
[ 1 ] CVE-2009-1373
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1373
[ 2 ] CVE-2009-1374
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1374
[ 3 ] CVE-2009-1375
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1375
[ 4 ] CVE-2009-1376
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1376
[ 5 ] GLSA 200901-13
http://www.gentoo.org/security/en/glsa/glsa-200901-13.xml
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
http://security.gentoo.org/glsa/glsa-200905-07.xml
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
http://bugs.gentoo.org.
License
=======
Copyright 2009 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.
http://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2009-05-25 23:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1243288741.7549.1.camel@localhost \
--to=a3li@gentoo.org \
--cc=bugtraq@securityfocus.com \
--cc=full-disclosure@lists.grok.org.uk \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security-alerts@linuxsecurity.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox