full-disclosure - [FLSA-2004:1733] Updated squirrelmail resolves security vulnerabilities

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20041002140859.GA10111@home.thedom.org>
From: dom at earth.li (Dominic Hargreaves)
Subject: [FLSA-2004:1733] Updated squirrelmail resolves security vulnerabilities

-----------------------------------------------------------------------
               Fedora Legacy Update Advisory

Synopsis:          Updated squirrelmail resolves security vulnerabilities
Advisory ID:       FLSA:1733
Issue date:        2004-10-02
Product:           Red Hat Linux
Keywords:          Security
Cross references:  https://bugzilla.fedora.us/show_bug.cgi?id=1733
CVE Names:         CAN-2004-0519, CAN-2004-0520, CAN-2004-0521
-----------------------------------------------------------------------

-----------------------------------------------------------------------
1. Topic:

Updated squirrelmail packages that fix a security vulnerability are now
available.

SquirrelMail is a standards-based webmail package written in PHP4.

2. Relevant releases/architectures:

Red Hat Linux 9 - i386

3. Problem description:

An SQL injection flaw was found in SquirrelMail version 1.4.2 and earlier.
If SquirrelMail is configured to store user addressbooks in the database, a
remote attacker could use this flaw to execute arbitrary SQL statements.
The Common Vulnerabilities and Exposures project has assigned the name
CAN-2004-0521 to this issue.

A number of cross-site scripting (XSS) flaws in SquirrelMail version 1.4.2
and earlier could allow remote attackers to execute script as other web
users. The Common Vulnerabilities and Exposures project (cve.mitre.org)
has assigned the names CAN-2004-0519 and CAN-2004-0520 to these issues.

Users of squirrelmail should upgrade to this updated package which
contains a new version of the software and 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 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 - 1733 - SquirrelMail Folder Name Cross-Site
Scripting Vulnerability

6. RPMs required:

Red Hat Linux 9:

SRPM:
http://download.fedoralegacy.org/redhat/9/updates/SRPMS/squirrelmail-1.4.3-0.f0.9.1.legacy.src.rpm

i386:
http://download.fedoralegacy.org/redhat/9/updates/i386/i386/squirrelmail-1.4.3-0.f0.9.1.legacy.noarch.rpm

7. Verification:

SHA1 sum                                 Package Name
---------------------------------------------------------------------------

c11465630aac1834c37b9af25dc77bccfd1785be  9/updates/SRPMS/squirrelmail-1.4.3-0.f0.9.1.legacy.src.rpm
de580a0c9f0b5d8129b0dc5b11671ce9c8e8446f  9/updates/i386/squirrelmail-1.4.3-0.f0.9.1.legacy.noarch.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://www.gentoo.org/security/en/glsa/glsa-200405-16.xml

9. Contact:

The Fedora Legacy security contact is <secnotice@...oralegacy.org>. More
project details at http://www.fedoralegacy.org

10. Special Notes:

Since this release is a version upgrade, care should be taken in
applying the update in a production environment.

---------------------------------------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20041002/d345b295/attachment.bin