1 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
2 |
Gentoo Linux Security Advisory GLSA 200701-10 |
3 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
4 |
http://security.gentoo.org/ |
5 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
6 |
|
7 |
Severity: Normal |
8 |
Title: WordPress: Multiple vulnerabilities |
9 |
Date: January 15, 2007 |
10 |
Bugs: #159229 |
11 |
ID: 200701-10 |
12 |
|
13 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
14 |
|
15 |
Synopsis |
16 |
======== |
17 |
|
18 |
WordPress is vulnerable to SQL injection, information disclosure, and |
19 |
cross-site scripting attacks. |
20 |
|
21 |
Background |
22 |
========== |
23 |
|
24 |
WordPress is a popular personal publishing platform with a web |
25 |
interface. |
26 |
|
27 |
Affected packages |
28 |
================= |
29 |
|
30 |
------------------------------------------------------------------- |
31 |
Package / Vulnerable / Unaffected |
32 |
------------------------------------------------------------------- |
33 |
1 www-apps/wordpress < 2.0.6 >= 2.0.6 |
34 |
|
35 |
Description |
36 |
=========== |
37 |
|
38 |
When decoding trackbacks with alternate character sets, WordPress does |
39 |
not correctly sanitize the entries before further modifying a SQL |
40 |
query. WordPress also displays different error messages in wp-login.php |
41 |
based upon whether or not a user exists. David Kierznowski has |
42 |
discovered that WordPress fails to properly sanitize recent file |
43 |
information in /wp-admin/templates.php before sending that information |
44 |
to a browser. |
45 |
|
46 |
Impact |
47 |
====== |
48 |
|
49 |
An attacker could inject arbitrary SQL into WordPress database queries. |
50 |
An attacker could also determine if a WordPress user existed by trying |
51 |
to login as that user, better facilitating brute force attacks. Lastly, |
52 |
an attacker authenticated to view the administrative section of a |
53 |
WordPress instance could try to edit a file with a malicious filename; |
54 |
this may cause arbitrary HTML or JavaScript to be executed in users' |
55 |
browsers viewing /wp-admin/templates.php. |
56 |
|
57 |
Workaround |
58 |
========== |
59 |
|
60 |
There is no known workaround at this time. |
61 |
|
62 |
Resolution |
63 |
========== |
64 |
|
65 |
All WordPress users should upgrade to the latest version: |
66 |
|
67 |
# emerge --sync |
68 |
# emerge --ask --oneshot --verbose ">=www-apps/wordpress-2.0.6" |
69 |
|
70 |
References |
71 |
========== |
72 |
|
73 |
[ 1 ] CVE-2006-6808 |
74 |
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6808 |
75 |
[ 2 ] CVE-2007-0107 |
76 |
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0107 |
77 |
[ 3 ] CVE-2007-0109 |
78 |
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0109 |
79 |
|
80 |
Availability |
81 |
============ |
82 |
|
83 |
This GLSA and any updates to it are available for viewing at |
84 |
the Gentoo Security Website: |
85 |
|
86 |
http://security.gentoo.org/glsa/glsa-200701-10.xml |
87 |
|
88 |
Concerns? |
89 |
========= |
90 |
|
91 |
Security is a primary focus of Gentoo Linux and ensuring the |
92 |
confidentiality and security of our users machines is of utmost |
93 |
importance to us. Any security concerns should be addressed to |
94 |
security@g.o or alternatively, you may file a bug at |
95 |
http://bugs.gentoo.org. |
96 |
|
97 |
License |
98 |
======= |
99 |
|
100 |
Copyright 2007 Gentoo Foundation, Inc; referenced text |
101 |
belongs to its owner(s). |
102 |
|
103 |
The contents of this document are licensed under the |
104 |
Creative Commons - Attribution / Share Alike license. |
105 |
|
106 |
http://creativecommons.org/licenses/by-sa/2.5 |