public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sune Kloppenborg Jeppesen <jaervosz@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 200606-08 ] WordPress: Arbitrary command execution
Date: Fri, 9 Jun 2006 23:10:59 +0200	[thread overview]
Message-ID: <200606092311.03672.jaervosz@gentoo.org> (raw)

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 200606-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  Severity: High
     Title: WordPress: Arbitrary command execution
      Date: June 09, 2006
      Bugs: #134397
        ID: 200606-08

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

Synopsis
========

WordPress fails to sufficiently check the format of cached username
data.

Background
==========

WordPress is a PHP and MySQL based content management and publishing
system.

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

    -------------------------------------------------------------------
     Package             /  Vulnerable  /                   Unaffected
    -------------------------------------------------------------------
  1  www-apps/wordpress       < 2.0.3                         >= 2.0.3

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

rgod discovered that WordPress insufficiently checks the format of
cached username data.

Impact
======

An attacker could exploit this vulnerability to execute arbitrary
commands by sending a specially crafted username. As of Wordpress 2.0.2
the user data cache is disabled as the default.

Workaround
==========

There are no known workarounds at this time.

Resolution
==========

All WordPress users should upgrade to the latest available version:

    # emerge --sync
    # emerge --ask --oneshot --verbose ">=www-apps/wordpress-2.0.3"

References
==========

  [ 1 ] CVE-2006-2667
        http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2667
  [ 2 ] CVE-2006-2702
        http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2702

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

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

  http://security.gentoo.org/glsa/glsa-200606-08.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 2006 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: 191 bytes --]

                 reply	other threads:[~2006-06-09 21:48 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=200606092311.03672.jaervosz@gentoo.org \
    --to=jaervosz@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