Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2004.0466 -- Two Fedora Legacy Update Advisories
Updated mailman resolves security vulnerability
and
Updated libxml2 resolves security vulnerability
22 July 2004
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: mailman
libxml2
Publisher: Red Hat
Operating System: Red Hat Linux - Fedora
Impact: Inappropriate Access
Execute Arbitrary Code/Commands
Access Required: Remote
CVE Names: CAN-2004-0412 CAN-2004-0110
- --------------------------BEGIN INCLUDED TEXT--------------------
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- - -----------------------------------------------------------------------
Fedora Legacy Update Advisory
Synopsis: Updated mailman resolves security vulnerability
Advisory ID: FLSA:1734
Issue date: 2004-07-19
Product: Red Hat Linux
Keywords: Bugfix
Cross references: https://bugzilla.fedora.us/show_bug.cgi?id=1734
CVE Names: CAN-2004-0412
- - -----------------------------------------------------------------------
- - ---------------------------------------------------------------------
1. Topic:
Updated mailman packages that fixes a remote security vulnerability are now
available.
2. Relevent releases/architectures:
Red Hat Linux 9 - i386
3. Problem description:
Mailman is software to help manage email discussion lists, much like
Majordomo and Smartmail. Unlike most similar products, Mailman gives each
mailing list a webpage, and allows users to subscribe, unsubscribe, etc.
over the Web. Even the list manager can administer his or her list
entirely from the Web. Mailman also integrates most things people want to
do with mailing lists, including archiving, mail <-> news gateways, and so
on.
A flaw in Mailman 2.1.* allows a remote attacker to retrieve the mailman
password of any subscriber by sending a carefully crafted email request to
the mailman server.
A simple patch is available and is fixed upstream in Mailman 2.1.5.
All users are advised to upgrade to these updated packages, which contain a
backported fix and are not vulnerable to this issue.
Fedora Legacy would like to thank Marc Deslauriers for reporting 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 yum and apt. Many
people find this an easier way to apply updates. To use yum issue:
yum update
or to use apt:
apt-get update; apt-get upgrade
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system. This assumes that you have yum or
apt-get configured for obtaining Fedora Legacy content. Please visit
http://www fedoralegacy.org/docs for directions on how to configure yum
and apt-get.
5. Bug IDs fixed:
http://bugzilla.fedora.us - 1734 - CAN-2004-0412 Mailman password retrieval
6. RPMs required:
Red Hat Linux 9:
SRPM: http://download.fedoralegacy.org/redhat/7.3/updates/SRPMS/mailman-2.1.1-7.legacy.src.rpm
i386: http://download.fedoralegacy.org/redhat/7.3/updates/i386/mailman-2.1.1-7.legacy.i386.rpm
7. Verification:
SHA1 sum Package Name
- - ---------------------------------------------------------------------------
4dee398d2d9b1d107850665f04c082073b4465a5
9/updates/SRPMS/mailman-2.1.1-7.legacy.src.rpm
66cbbfcf168869969b0aaa0298d3680c3b8e5a3c
9/updates/i386/mailman-2.1.1-7.legacy.i386.rpm
These packages are GPG signed by Fedora Legacy for security. Our key is
available from http://www.fedoralegacy org/about/security.php
You can verify each package with the following command:
rpm --checksig -v <filename>
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the sha1sum with the following command:
sha1sum <filename>
8. References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0412
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123559
http://mail.python.org/pipermail/mailman-announce/2004-May/000072.html
9. Contact:
The Fedora Legacy security contact is <secnotice@fedoralegacy.org>. More
project details at http://www.fedoralegacy.org
- - ---------------------------------------------------------------------
- - --
Jesse Keating RHCE (http://geek.j2solutions.net)
Fedora Legacy Team (http://www.fedoralegacy.org)
GPG Public Key (http://geek.j2solutions.net/jkeating.j2solutions.pub)
Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA/KA94v2HLvE71NURAt/3AJ942eiZGscchS/7odKEbHIBdHiTkQCdFZ7A
lw5W/vaFcRxviBD3grWB6bs=
=dSXw
- -----END PGP SIGNATURE-----
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- - -----------------------------------------------------------------------
Fedora Legacy Update Advisory
Synopsis: Updated libxml2 resolves security vulnerability
Advisory ID: FLSA:1324
Issue date: 2004-07-19
Product: Red Hat Linux
Keywords: Security
Cross references: https://bugzilla.fedora.us/show_bug.cgi?id=1324
CVE Names: CAN-2004-0110
- - -----------------------------------------------------------------------
- - ---------------------------------------------------------------------
1. Topic:
Updated libxml2 packages that fix an overflow when parsing remote resources
are now available.
2. Relevent releases/architectures:
Red Hat Linux 7.3 - i386
3. Problem description:
libxml2 is a library for manipulating XML files.
Yuuichi Teranishi discovered a flaw in libxml2 versions prior to 2.6.6.
When fetching a remote resource via FTP or HTTP, libxml2 uses special
parsing routines. These routines can overflow a buffer if passed a very long URL.
If an attacker is able to find an application using libxml2 that
parses remote resources and allows them to influence the URL, then this
flaw could be used to execute arbitrary code. The Common Vulnerabilities and
Exposures project (cve.mitre.org) has assigned the name CAN-2004-0110
to this issue.
All users are advised to upgrade to these updated packages, which contain a
backported fix and are not vulnerable to this issue.
Fedora Legacy would like to thank Johnny Strom for reporting 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 yum and apt. Many
people find this an easier way to apply updates. To use yum issue:
yum update
or to use apt:
apt-get update; apt-get upgrade
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system. This assumes that you have yum or
apt-get configured for obtaining Fedora Legacy content. Please visit
http://www fedoralegacy.org/docs for directions on how to configure yum
and apt-get.
5. Bug IDs fixed:
http://bugzilla.fedora.us - 1324 - libxml2: an overflow when parsing remote
resources.
6. RPMs required:
Red Hat Linux 7.3:
SRPM: http://download.fedoralegacy.org/redhat/7.3/updates/SRPMS/libxml2-2.4.19-5.legacy.src.rpm
i386: http://download.fedoralegacy.org/redhat/7.3/updates/i386/libxml2-2.4.19-5.legacy.i386.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/libxml2-python-2.4.19-5.legacy.i386.rpm
http://download.fedoralegacy.org/redhat/7.3/updates/i386/libxml2-devel-2.4.19-5.legacy.i386.rpm
7. Verification:
SHA1 sum Package Name
- - ---------------------------------------------------------------------------
7ea6c8e40a04c2eafb82d53e8e6931b27348f4ad
7.3/updates/SRPMS/libxml2-2.4.19-5.legacy.src.rpm
c325b2b9d03335b41db6b0b462a35d1ed847e56f
7.3/updates/i386/libxml2-2.4.19-5.legacy.i386.rpm
c53f70cad435630b3e5b5f5d363c7d425f980a35
7.3/updates/i386/libxml2-devel-2.4.19-5.legacy.i386.rpm
8819fa789731693645839f32f55aac2f2dc27906
7.3/updates/i386/libxml2-python-2.4.19-5.legacy.i386.rpm
These packages are GPG signed by Fedora Legacy for security. Our key is
available from http://www.fedoralegacy org/about/security.php
You can verify each package with the following command:
rpm --checksig -v <filename>
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the sha1sum with the following command:
sha1sum <filename>
8. References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0110
https://www.redhat.com/archives/redhat-watch-list/2004-February/msg00007.html
http://mail.gnome.org/archives/xml/2004-February/msg00070.html
9. Contact:
The Fedora Legacy security contact is <secnotice@fedoralegacy.org>. More
project details at http://www.fedoralegacy.org
- - ---------------------------------------------------------------------
- - --
Jesse Keating RHCE (http://geek.j2solutions.net)
Fedora Legacy Team (http://www.fedoralegacy.org)
GPG Public Key (http://geek.j2solutions.net/jkeating.j2solutions.pub)
Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA/JVx4v2HLvE71NURAk+sAKCtr5UVXfrGLhkoHxfi5BHyDLtBmQCgum0l
5hirw0+x3WPmJhPz+nqydX4=
=Xs3j
- -----END PGP SIGNATURE-----
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
If you believe that your computer system has been compromised or attacked in
any way, we encourage you to let us know by completing the secure National IT
Incident Reporting Form at:
http://www.auscert.org.au/render.html?it=3192
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business
hours which are GMT+10:00 (AEST). On call after hours
for member emergencies only.
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQCVAwUBQP862ih9+71yA2DNAQKUiAP/YLeJeJGHnVUvTlIA3xKEoj5S6vi86W8g
90/ey7lVSw8rrp9gsFALfE74CIW6FRWfzGwTsMd5QW0CfCV9Vi2v1+DmnD/3h+11
AfuYN1UI0c5F6/iJWqmGSyHb6Sbk6XoKfzJTsOSs2/uEo/VE9fyZsmYPIfSbdGUz
vgvDuk38JJ4=
=IVLg
-----END PGP SIGNATURE-----