public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thierry Carrez <koon@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 200506-02 ] Mailutils: SQL Injection
Date: Mon, 06 Jun 2005 18:20:02 +0200	[thread overview]
Message-ID: <42A477B2.7000901@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2510 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 200506-02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  Severity: Normal
     Title: Mailutils: SQL Injection
      Date: June 06, 2005
      Bugs: #94824
        ID: 200506-02

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

Synopsis
========

GNU Mailutils is vulnerable to SQL command injection attacks.

Background
==========

GNU Mailutils is a collection of mail-related utilities.

Affected packages
=================

    -------------------------------------------------------------------
     Package             /  Vulnerable  /                   Unaffected
    -------------------------------------------------------------------
  1  net-mail/mailutils      < 0.6-r1                        >= 0.6-r1

Description
===========

When GNU Mailutils is built with the "mysql" or "postgres" USE flag,
the sql_escape_string function of the authentication module fails to
properly escape the "\" character, rendering it vulnerable to a SQL
command injection.

Impact
======

A malicious remote user could exploit this vulnerability to inject SQL
commands to the underlying database.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All GNU Mailutils users should upgrade to the latest available version:

    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-mail/mailutils-0.6-r1"

References
==========

  [ 1 ] CAN-2005-1824
        http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-1824

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

  http://security.gentoo.org/glsa/glsa-200506-02.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 2005 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.0


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2005-06-06 16:20 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=42A477B2.7000901@gentoo.org \
    --to=koon@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