Comments on: Vulnerability in WP Super Cache v0.1 http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/ This can all be made better. Ready? Begin. Mon, 01 Dec 2008 19:48:27 +0000 http://wordpress.org/?v=2.6.5 By: DG http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-97260 DG Tue, 04 Dec 2007 13:20:17 +0000 http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-97260 Chris, I've noticed similiar activites on my site about 20 days back, and since then, I was busy checking all my template/plugin files, but couldn't find any unusual thing therein. Yesterday, I was zeored on to WordPress Super Cache, as that was the only plugin left unchecked. Later on, further digging confirmed my doubt and also came across your post. I've written to donnacha on his email as well in your WordPress support forum thread about the vulnerability still exisiting in the latest version. DG... Chris,

I’ve noticed similiar activites on my site about 20 days back, and since then, I was busy checking all my template/plugin files, but couldn’t find any unusual thing therein.

Yesterday, I was zeored on to WordPress Super Cache, as that was the only plugin left unchecked. Later on, further digging confirmed my doubt and also came across your post.

I’ve written to donnacha on his email as well in your WordPress support forum thread about the vulnerability still exisiting in the latest version.

DG…

]]> By: DG http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-97251 DG Tue, 04 Dec 2007 00:39:27 +0000 http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-97251 Hello Chris, The vulnerability, you mentioned still exisits, even in the newest version 0.5.1. I had seen similiar deeply nested folders in my root directory about 20 days ago. Since than, I'm checking all my template files and plugins, but couldn't find anything unusual. Today, I checked WordPress Super Cache, as it was the only plugin that was unleft and found the cause behind the vulnerability. After digging further, I came across your post, which confirmed the issue. DG... http://www.ditii.com/ Hello Chris,

The vulnerability, you mentioned still exisits, even in the newest version 0.5.1.

I had seen similiar deeply nested folders in my root directory about 20 days ago. Since than, I’m checking all my template files and plugins, but couldn’t find anything unusual.

Today, I checked WordPress Super Cache, as it was the only plugin that was unleft and found the cause behind the vulnerability.

After digging further, I came across your post, which confirmed the issue.

DG…
http://www.ditii.com/

]]> By: WP Super Cache should be safe to use | Tummblr http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-96486 WP Super Cache should be safe to use | Tummblr Mon, 12 Nov 2007 02:21:37 +0000 http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-96486 [...] directory but nothing more. That bug has been fixed. See Donncha’s official statement and Chris’s account of the bug and debugging process in more detail. Thanks, Donncha, for the speedy resolution of this [...] [...] directory but nothing more. That bug has been fixed. See Donncha’s official statement and Chris’s account of the bug and debugging process in more detail. Thanks, Donncha, for the speedy resolution of this [...]

]]> By: Greg Knaddison http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-96470 Greg Knaddison Sat, 10 Nov 2007 13:07:14 +0000 http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-96470 There's a remotely exploitable security hole that allows the installation of a shellbot and the best Barry can say is "just a bug" and "misdirected attack on potentially vulnerably Drupal sites". Way to ignore and redirect what seems clearly like a real problem with a WordPress plugin that was targetted itself. If you make a claim like "probably misdirected attack on Drupal" you should provide an in depth analysis that shows exactly why a script to exploit a Drupal vulnerability is in fact accidentally exploiting this wordpress vulnerability. There’s a remotely exploitable security hole that allows the installation of a shellbot and the best Barry can say is “just a bug” and “misdirected attack on potentially vulnerably Drupal sites”.

Way to ignore and redirect what seems clearly like a real problem with a WordPress plugin that was targetted itself.

If you make a claim like “probably misdirected attack on Drupal” you should provide an in depth analysis that shows exactly why a script to exploit a Drupal vulnerability is in fact accidentally exploiting this wordpress vulnerability.

]]> By: Donncha’s Friday Links at Holy Shmoly! http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-96465 Donncha’s Friday Links at Holy Shmoly! Fri, 09 Nov 2007 15:40:50 +0000 http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-96465 [...] is no vulnerability in WP Super Cache. Chris blogged about it after we spent a late night of debugging it until 1.30am. But [...] [...] is no vulnerability in WP Super Cache. Chris blogged about it after we spent a late night of debugging it until 1.30am. But [...]

]]> By: Christian Heilmann http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-96461 Christian Heilmann Fri, 09 Nov 2007 07:50:53 +0000 http://factoryjoe.com/blog/2007/11/08/vulnerability-in-wp-super-cache-v01/#comment-96461 I have to concur, Donncha has been very interested and helpful about this. I talked to the security experts at work about the attacks and they are very common these days. The best prevention is to turn off any passthru, exec or other shell extensions and disallow file loading from http. I have to concur, Donncha has been very interested and helpful about this. I talked to the security experts at work about the attacks and they are very common these days. The best prevention is to turn off any passthru, exec or other shell extensions and disallow file loading from http.

]]>