metadata/glsa/glsa-200611-10.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200611-10">
  <title>WordPress: Multiple vulnerabilities</title>
  <synopsis>
    Flaws in WordPress allow a Denial of Service, the disclosure of user
    metadata and the overwriting of restricted files.
  </synopsis>
  <product type="ebuild">wordpress</product>
  <announced>2006-11-17</announced>
  <revised count="01">2006-11-17</revised>
  <bug>153303</bug>
  <access>remote</access>
  <affected>
    <package name="www-apps/wordpress" auto="yes" arch="*">
      <unaffected range="ge">2.0.5</unaffected>
      <vulnerable range="lt">2.0.5</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    WordPress is a PHP and MySQL based multiuser blogging system.
    </p>
  </background>
  <description>
    <p>
    "random" discovered that users can enter serialized objects as strings
    in their profiles that will be harmful when unserialized. "adapter"
    found out that user-edit.php fails to effectively deny non-permitted
    users access to other user's metadata. Additionally, a directory
    traversal vulnerability in the wp-db-backup module was discovered.
    </p>
  </description>
  <impact type="normal">
    <p>
    By entering specially crafted strings in his profile, an attacker can
    crash PHP or even the web server running WordPress. Additionally, by
    crafting a simple URL, an attacker can read metadata of any other user,
    regardless of their own permissions. A user with the permission to use
    the database backup plugin can possibly overwrite files he otherwise
    has no access to.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All WordPress users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=www-apps/wordpress-2.0.5"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5705">CVE-2006-5705</uri>
    <uri link="https://trac.wordpress.org/ticket/3142">WordPress Ticket 3142</uri>
    <uri link="https://trac.wordpress.org/ticket/2591">WordPress Ticket 2591</uri>
  </references>
  <metadata tag="submitter" timestamp="2006-11-08T12:56:04Z">
    frilled
  </metadata>
  <metadata tag="bugReady" timestamp="2006-11-09T06:33:42Z">
    frilled
  </metadata>
</glsa>