Date: Thu, 24 Apr 2003 17:03 -0400
From: [email protected]
To: [email protected], [email protected]Subject: [RHSA-2003:118-01] Updated mICQ packages fix vulnerability
---------------------------------------------------------------------
Red Hat Security Advisory
Synopsis: Updated mICQ packages fix vulnerability
Advisory ID: RHSA-2003:118-01
Issue date: 2003-04-24
Updated on: 2003-04-24
Product: Red Hat Linux
Ключевые слова:, , , , , , , , , mICQ, malformed, ICQ, message, DoS, 0xFE, (найти похожие документы)
Cross references:=20=20
Obsoletes:=20=20=20=20=20=20=20=20=20
CVE Names: CAN-2002-1363
---------------------------------------------------------------------
1. Topic:
Updated mICQ packages are available for Red Hat Linux versions 7.2 and 7.3
that fix a remote crash.
2. Relevant releases/architectures:
Red Hat Linux 7.2 - i386, ia64
Red Hat Linux 7.3 - i386
3. Problem description:
mICQ is an online messaging and conferencing program.
mICQ versions 0.4.9 and earlier allow remote attackers to cause a denial of
service (crash) using malformed ICQ message types without a 0xFE separator
character.
Users of mICQ are advised to upgrade to these erratum packages containing
mICQ version 0.4.10.2 which is not vulnerable to this issue.
4. Solution:
Before applying this update, make sure all previously released errata
relevant to your system have been applied.
To update all RPMs for your particular architecture, run:
rpm -Fvh [filenames]
where [filenames] is a list of the RPMs you wish to upgrade. Only those
RPMs which are currently installed will be updated. Those RPMs which are
not installed but included in the list will not be updated. Note that you
can also use wildcards (*.rpm) if your current directory *only* contains the
desired RPMs.
Please note that this update is also available via Red Hat Network. Many
people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:
up2date
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.
5. RPMs required:
Red Hat Linux 7.2:
SRPMS:
ftp://updates.redhat.com/7.2/en/os/SRPMS/micq-0.4.10.2-1.src.rpm
i386:
ftp://updates.redhat.com/7.2/en/os/i386/micq-0.4.10.2-1.i386.rpm
ia64:
ftp://updates.redhat.com/7.2/en/os/ia64/micq-0.4.10.2-1.ia64.rpm
Red Hat Linux 7.3:
SRPMS:
ftp://updates.redhat.com/7.3/en/os/SRPMS/micq-0.4.10.2-1.src.rpm
i386:
ftp://updates.redhat.com/7.3/en/os/i386/micq-0.4.10.2-1.i386.rpm
6. Verification:
MD5 sum Package Name
--------------------------------------------------------------------------
e31356211e259ae60d0f15cc42313b4b 7.2/en/os/SRPMS/micq-0.4.10.2-1.src.rpm
bf2a680539f10a6acbd5d461ba8fc0f7 7.2/en/os/i386/micq-0.4.10.2-1.i386.rpm
9c2e01528840d2a4b60f9185f86e0556 7.2/en/os/ia64/micq-0.4.10.2-1.ia64.rpm
e31356211e259ae60d0f15cc42313b4b 7.3/en/os/SRPMS/micq-0.4.10.2-1.src.rpm
bf2a680539f10a6acbd5d461ba8fc0f7 7.3/en/os/i386/micq-0.4.10.2-1.i386.rpm
These packages are GPG signed by Red Hat for security. Our key is
available at http://www.redhat.com/solutions/security/news/publickey/
You can verify each package with the following command:
=20=20=20=20
rpm --checksig -v <filename>
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the md5sum with the following command:
=20=20=20=20
md5sum <filename>
7. References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCAN-2002-1363
8. Contact:
The Red Hat security contact is <[email protected]>. More contact
details at http://www.redhat.com/solutions/security/news/contact/
Copyright 2003 Red Hat, Inc.
