<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>202071</bug_id>
          <alias>CVE-2007-6318</alias>
          <creation_ts>2007-12-12 18:23 0000</creation_ts>
          <short_desc>www-apps/wordpress &lt; 2.3.2 SQL injection vulnerability (CVE-2007-6318)</short_desc>
          <delta_ts>2008-01-08 08:21:12 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Security</product>
          <component>Vulnerabilities</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          <bug_file_loc>http://www.abelcheung.org/advisory/20071210-wordpress-charset.txt</bug_file_loc>
          <status_whiteboard>~3 [noglsa]</status_whiteboard>
          
          <priority>P2</priority>
          <bug_severity>trivial</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>lars@chaotika.org</reporter>
          <assigned_to>security@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>lars@chaotika.org</who>
            <bug_when>2007-12-12 18:23:35 0000</bug_when>
            <thetext>SQL injection vulnerability in wp-includes/query.php in WordPress 2.3.1 and
earlier allows remote attackers to execute arbitrary SQL commands via the s
parameter, when DB_CHARSET is set to (1) Big5, (2) GBK, or possibly other
character set encodings that support a &quot;\&quot; in a multibyte character.

Reproducible: Always</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>rbu@gentoo.org</who>
            <bug_when>2007-12-13 01:28:03 0000</bug_when>
            <thetext>Feel free to cc maintainers and set a whiteboard as proposal yourself ;-)

</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>rbu@gentoo.org</who>
            <bug_when>2007-12-13 01:28:21 0000</bug_when>
            <thetext>web-apps, please advise.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wrobel@gentoo.org</who>
            <bug_when>2007-12-13 06:23:34 0000</bug_when>
            <thetext>No patch available and I don&apos;t see a chance at fixing it myself. Should we mask it again? </thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>thoger@redhat.com</who>
            <bug_when>2007-12-13 07:50:31 0000</bug_when>
            <thetext>Upstream bug: http://trac.wordpress.org/ticket/5455</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>rbu@gentoo.org</who>
            <bug_when>2007-12-13 12:22:05 0000</bug_when>
            <thetext>(In reply to comment #3)
&gt; No patch available and I don&apos;t see a chance at fixing it myself. Should we mask
&gt; it again? 

No need to jump to a mask if we can fix it within target delay, which is 40 days for ~X. Let&apos;s give the Wordpress folks some days.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wrobel@gentoo.org</who>
            <bug_when>2008-01-08 06:30:26 0000</bug_when>
            <thetext>Added 2.3.2 to the tree. All archs unstable. Removed insecure versions. webapps done here.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>