Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
From: Martin Schulze (joey_at_infodrom.org)
Date: Wed Jan 15 2003 - 09:15:42 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Hash: SHA1

    - --------------------------------------------------------------------------
    Debian Security Advisory DSA 229-1 securitydebian.org
    http://www.debian.org/security/ Martin Schulze
    January 15th, 2003 http://www.debian.org/security/faq
    - --------------------------------------------------------------------------

    Package : imp
    Vulnerability : SQL injection
    Problem-Type : remote
    Debian-specific: no
    CVE Id : CAN-2003-0025

    Jouko Pynnonen discovered a probem with IMP, a web based IMAP mail
    program. Using carefully crafted URLs a remote attacker is able to
    inject SQL code into SQL queries without proper user authentication.
    Even though results of SQL queries aren't directly readable from the
    screen, an attacker might. update his mail signature to contain wanted
    query results and then view it on the preferences page of IMP.

    The impact of SQL injection depends heavily on the underlying database
    and its configuration. If PostgreSQL is used, it's possible to
    execute multiple complete SQL queries separated by semicolons. The
    database contains session id's so the attacker might hijack sessions
    of people currently logged in and read their mail. In the worst case,
    if the hordemgr user has the required privilege to use the COPY SQL
    command (found in PostgreSQL at least), a remote user may read or
    write to any file the database user (postgres) can. The attacker may
    then be able to run arbitrary shell commands by writing them to the
    postgres user's ~/.psqlrc; they'd be run when the user starts the psql
    command which under some configurations happens regularly from a cron

    For the current stable distribution (woody) this problem has been
    fixed in version 2.2.6-5.1.

    For the old stable distribution (potato) this problem has been
    fixed in version 2.2.6-0.potato.5.1.

    For the unstable distribution (sid) these problems have been fixed in
    version 2.2.6-7.

    We recommend that you upgrade your IMP packages.

    Upgrade Instructions
    - --------------------

    wget url
            will fetch the file for you
    dpkg -i file.deb
            will install the referenced file.

    If you are using the apt-get package manager, use the line for
    sources.list as given below:

    apt-get update
            will update the internal database
    apt-get upgrade
            will install corrected packages

    You may use an automated update by adding the resources from the
    footer to the proper configuration.

    Debian GNU/Linux 2.2 alias potato
    - ---------------------------------

      Source archives:

          Size/MD5 checksum: 557 76665368f11feb7adce9796815821d04
          Size/MD5 checksum: 66837 18cfcbbc6eb09ed11085e84701cb1ffb

      Architecture independent components:

          Size/MD5 checksum: 410972 acf2cfbd75191cdcb68ec714b22d2adf

    Debian GNU/Linux 3.0 alias woody
    - --------------------------------

      Source archives:

          Size/MD5 checksum: 638 8d877729002750b2962eff3b14294bb9
          Size/MD5 checksum: 95177 47ca6f61febbe839fc27f4e53f8fde8d

      Architecture independent components:

          Size/MD5 checksum: 426826 134e3d543d2d32f1fe9f84664a819dd0

      These files will probably be moved into the stable distribution on
      its next revision.

    - ---------------------------------------------------------------------------------
    For apt-get: deb http://security.debian.org/ stable/updates main
    For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
    Mailing list: debian-security-announcelists.debian.org
    Package info: `apt-cache show <pkg>' and http://packages.debian.org/>

    Version: GnuPG v1.2.1 (GNU/Linux)

    -----END PGP SIGNATURE-----