Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: [Full-disclosure] Wordpress Cookie Authentication Vulnerability |
|---|---|
| Date: | Thu, 22 Nov 2007 16:56:00 +0200 (EET) |
This issue is SA27714 (severity 1/5) http://secunia.com/advisories/27714/ and FrSIRT/ADV-2007-3941 (severity 1/4) http://www.frsirt.com/english/advisories/2007/3941 too. Secunia advisory lists these workarounds: "Grant only trusted users read access to the "users" table. Restrict access to the "wp-admin" directory (e.g. with ".htaccess")." - Juha-Matti
Right this problem has existed for a long time, but it's not the end of the world for someone to point it out again I suppose. I think it's obvious that there's another main issue here and that's the way WordPress handles its cookies in general. They are not temporary sessions that expire or are only valid upon successful authentication. The cookies work for ever.. or at least until the password changes. If someone uses an XSS attack to obtain the cookies or sniffs them (most blogs are just HTTP) they can essentially permanently authenticate. The same result occurs with being able to read the database. Furthermore, one could in theory conduct a bruteforce attack against the WordPress password by just making normal requests to the blog but changing the cookies that does the double MD5 of the password. You could in theory emulate normal continued browsing of the website while sending MD5(MD5(password)) over and over with each request via the cookie. Other than perhaps a large increase in browsing of the blog, this could possibly go unnoticed as an attack -- as it would not be logged anywhere (in most instances) that the cookies were being presented. Once authenticated into WordPress, the normal blog pages look different, so it would not require an attacker to access the Admin area to verify. Anyway, good to see the CVE is already there. Maybe better session management will find its way into WordPress. Steven http://www.securityzone.org
(>..runs on WordPress.. oh noes!)
This is CVE-2007-6013 since 19th Nov including WordPress ticket #5367: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6013 - Juha-Matti
--clip-- _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Full-disclosure] Knowing you're Secure!, rchrafe |
|---|---|
| Next by Date: | [Full-disclosure] [ MDKSA-2007:231 ] - Updated cacti packages fix SQL injection vulnerability, security |
| Previous by Thread: | Re: [Full-disclosure] Wordpress Cookie Authentication Vulnerability, Adrian P |
| Next by Thread: | [Full-disclosure] [ GLSA 200711-28 ] Perl: Buffer overflow, Pierre-Yves Rofes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |