public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Raphael Marichez <falco@gentoo.org>
To: gentoo-announce@gentoo.org
Cc: bugtraq@securityfocus.com, full-disclosure@lists.grok.org.uk,
	security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 200710-28 ] Qt: Buffer overflow
Date: Thu, 25 Oct 2007 23:46:24 +0200	[thread overview]
Message-ID: <20071025214624.GD13985@falco.falcal.net> (raw)

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 200710-28
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  Severity: Normal
     Title: Qt: Buffer overflow
      Date: October 25, 2007
      Bugs: #192472
        ID: 200710-28

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

Synopsis
========

An off-by-one vulnerability has been discovered in Qt, possibly
resulting in the execution of arbitrary code.

Background
==========

Qt is a cross-platform GUI framework, which is used e.g. by KDE.

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

    -------------------------------------------------------------------
     Package      /  Vulnerable  /                          Unaffected
    -------------------------------------------------------------------
  1  x11-libs/qt     < 3.3.8-r4                            >= 3.3.8-r4

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

Dirk Mueller from the KDE development team discovered a boundary error
in file qutfcodec.cpp when processing Unicode strings.

Impact
======

A remote attacker could send a specially crafted Unicode string to a
vulnerable Qt application, possibly resulting in the remote execution
of arbitrary code with the privileges of the user running the
application. Note that the boundary error is present but reported to be
not exploitable in 4.x series.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All Qt 3.x users should upgrade to the latest version:

    # emerge --sync
    # emerge --ask --oneshot --verbose ">=x11-libs/qt-3.3.8-r4"

References
==========

  [ 1 ] CVE-2007-4137
        http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4137

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

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

  http://security.gentoo.org/glsa/glsa-200710-28.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 2007 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.5

[-- Attachment #2: Type: application/pgp-signature, Size: 481 bytes --]

                 reply	other threads:[~2007-10-25 22:09 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=20071025214624.GD13985@falco.falcal.net \
    --to=falco@gentoo.org \
    --cc=bugtraq@securityfocus.com \
    --cc=full-disclosure@lists.grok.org.uk \
    --cc=gentoo-announce@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