glsa-200703-23.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
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200703-23">
  <title>WordPress: Multiple vulnerabilities</title>
  <synopsis>
    Wordpress contains several cross-site scripting, cross-site request forgery
    and information leak vulnerabilities.
  </synopsis>
  <product type="ebuild">wordpress</product>
  <announced>2007-03-20</announced>
  <revised>2007-03-20: 01</revised>
  <bug>168529</bug>
  <access>remote</access>
  <affected>
    <package name="www-apps/wordpress" auto="yes" arch="*">
      <vulnerable range="le">2.1.2</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    WordPress is a popular personal publishing platform with a web
    interface.
    </p>
  </background>
  <description>
    <p>
    WordPress contains cross-site scripting or cross-site scripting forgery
    vulnerabilities reported by:
    </p>
    <ul><li>g30rg3_x in the "year"
    parameter of the wp_title() function</li>
    <li>Alexander Concha in the
    "demo" parameter of wp-admin/admin.php</li>
    <li>Samenspender and Stefan
    Friedli in the "post" parameter of wp-admin/post.php and
    wp-admin/page.php, in the "cat_ID" parameter of wp-admin/categories.php
    and in the "c" parameter of wp-admin/comment.php</li>
    <li>PsychoGun in
    the "file" parameter of wp-admin/templates.php</li>
    </ul> <p>
    </p>
    <p>
    Additionally, WordPress prints the full PHP script paths in some error
    messages.
    </p>
  </description>
  <impact type="low">
    <p>
    The cross-site scripting vulnerabilities can be triggered to steal
    browser session data or cookies. A remote attacker can entice a user to
    browse to a specially crafted web page that can trigger the cross-site
    request forgery vulnerability and perform arbitrary WordPress actions
    with the permissions of the user. Additionally, the path disclosure
    vulnerability could help an attacker to perform other attacks.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time for all these
    vulnerabilities.
    </p>
  </workaround>
  <resolution>
    <p>
    Due to the numerous recently discovered vulnerabilities in WordPress,
    this package has been masked in the portage tree. All WordPress users
    are advised to unmerge it.
    </p>
    <code>
    
    # emerge --unmerge "www-apps/wordpress"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-1049">CVE-2007-1049</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-1230">CVE-2007-1230</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-1244">CVE-2007-1244</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-1409">CVE-2007-1409</uri>
    <uri link="https://secunia.com/advisories/24430/">SA 24430</uri>
  </references>
  <metadata tag="requester" timestamp="2007-03-09T22:36:03Z">
    falco
  </metadata>
  <metadata tag="submitter" timestamp="2007-03-17T15:44:31Z">
    falco
  </metadata>
  <metadata tag="bugReady" timestamp="2007-03-20T11:36:10Z">
    falco
  </metadata>
</glsa>