This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • bobjonkman repeated a notice by silverwizard 13 November 2018
      RT @silverwizard ♲ @Roman 🐡 (romanzolotarev@twitter.com): Dear web developers, Make sure web pages you make work without #JavaScript too. Yes, you can do a lot with just HTML and CSS. Please make the web fast and clean. Thank you.
    • Favorite 13 November 2018
      bobjonkman favorited something by silverwizard: ♲ @Roman 🐡 (romanzolotarev@twitter.com): Dear web developers,Make sure web pages you make work without #JavaScript too.Yes, you can do a lot with just HTML and CSS.Please make the web fast and clean.Thank you.
    • bobjonkman repeated a notice by hattiecat 11 November 2018
      RT @hattiecat Looking at compile options for various things. Stuff like "sanity check - detect buffer overflows. Used for debugging. Slight overhead. Disable for production". IMO it's "disable for production" idiocy despite the minuscule perf. penalty that's responsible for a lot of breakage. Brings to mind again C.A.R. Hoare's remarks about having lifejackets on in […]
    • Favorite 11 November 2018
      bobjonkman favorited something by hattiecat: Looking at compile options for various things. Stuff like "sanity check - detect buffer overflows. Used for debugging. Slight overhead. Disable for production". IMO it's "disable for production" idiocy despite the minuscule perf. penalty that's responsible for a lot of breakage. Brings to mind again C.A.R. Hoare's remarks about having […]
    • New note by bobjonkman 10 November 2018
      Hm. That's @clacke... Any relation to #LibrePlanet, the @FSF user communities?
    • New note by bobjonkman 10 November 2018
      Thanx Claes! Nice to be back. Gotta set up a persistent #IRC client on my Comm server so I'm not dependent on different clients on different machines. ♻ @clacke@libreplanet.de: freenode #social
    • bobjonkman repeated a notice by radikal 10 November 2018
      RT @radikal @bobjonkman i am running an instance of !gnusocial over #PHP7, and works fine
    • Favorite 10 November 2018
      bobjonkman favorited something by radikal: @bobjonkman i am running an instance of !gnusocial over #PHP7, and works fine
    • Favorite 10 November 2018
      bobjonkman favorited something by clacke: freenode #social
    • bobjonkman repeated a notice by clacke 10 November 2018
      RT @clacke freenode #social

Recovering from a WordPress hack

Posted by Bob Jonkman on 29th October 2013

WordPress logo cleaved by axe

WordPress Hacked!

Last Friday I was finally getting around to upgrading the WordPress installations on the SOBAC server from v3.6 to v3.6.1. Surprise! WordPress v3.7 had just been released the night before!

WordPress upgrades are famous for their ease of installation. Surprise! After upgrading the first installation most of the plugins were missing, and the theme was broken. A quick look at a directory listing showed that the plugins and themes were still installed. A quick look with a text editor showed some peculiar PHP code at the top of every .php file in the plugins folders. Surprise! This WordPress installation had been hacked! Fortunately, of the five instances of WordPress on this server, only two appeared to be affected. This Blog Is Not For Reading was not one of them.

Each .php file started with something like this:

<?php $zend_framework="\x63\162\x65(…)\x6e"; 
@error_reporting(0); 
zend_framework("", "\x7d\7(…)

Injected, obfuscated PHP code at the top of every .php file, referencing the zend_framework

Searching the Internet for “wordpress plugin invalid header zend_framework” I found a reference that makes me think this may have been possible because of a flaw in an earlier version of the WordPress code that handles comments. Most likely one of the comment fields (user name, e-mail, web address or the comment text itself) wasn’t properly sanitized, and allowed some kind of code injection (probably PHP injection, not a MySQL injection; the contents of the databases appeared to be untouched).

From the backups of the server it appeared that the breach occurred in or before August — either just before the release of WordPress 3.6 on 1 August 2013 or just before the release of WordPress 3.6.1 on 11 September 2013. If I had not been slack in upgrading to WP v3.6.1 then this breach might have been identified much sooner.

The upgrade to WordPress identified the modified files because the injected code preceded (and corrupted) the WP headers, and so WP v3.7 disabled any affected plugins and themes.

The Fix Is In

I renamed the directory containing the WordPress code, installed a fresh copy of WP3.7, cleaned and copied the wp-config.php and .htaccess files, uploaded a small image to create the wp-content/uploads hierarchy, then copied the upload folder (which didn’t contain any .php files), and then re-installed and re-configured the themes and plugins directly from the WordPress site.

Aside from the additional PHP code, there didn’t appear to be any other damage to the system. So I used the original wp-config.php (but cleaned, and with the “Authentication Unique Keys and Salts” section refreshed), and the new installation just used the existing databases. If there’s any malcode in the databases then that could re-infect the system, so I’m keeping an eye on it.

I have no idea what the malcode was intended to do. It didn’t corrupt the databases or anything else, but it’s possible it was acting as a keylogger or phoning home some other way. If I feel inclined I might try to de-obfuscate the injected code, but right now I don’t really feel like doing forensics.

Someone suggested using AppArmor to make the WordPress directories read-only. I’m not sure that locking down the WP directory is a good idea. The big new feature in WordPress 3.7 is its automatic update feature. If the WordPress directories are locked down then future security updates won’t be applied automatically. If there is an exploit and WordPress issues a new release to fix it, then a locked-down site will experience a delay in upgrading until the SysAdmin notices and upgrades manually (which is what used to happen before v3.7, but it seems a bad idea to delay upgrades when that’s no longer necessary). Also, the plugin and themes directories would be locked down, and they still require fairly frequent manual upgrades.

I sent the users on the affected sites this message:

While doing upgrades on WordPress yesterday I saw that your blog had been hacked sometime during or before August. I’ve fixed it (re-installed the code, copied your media library, re-installed themes and plugins). I don’t think any damage was done beyond the insertion of malicious code in some of the WordPress files. I don’t know what the action of that code was intended to be, but you should change your WordPress password just in case the bad guys captured it. You can change your password on the “Users, Your Profile page” once you’ve logged in.

After spending some time on Saturday fixing the two hacked WordPress sites I’m a little paranoid, and making sure to implement updates quickly. But a little paranoia is good — it’ll ensure I won’t become complacent again.

–Bob.

WordPress Hacks by Rafael Poveda is used under a CC BY-NC-SACreative Commons — Attribution-NonCommercial-ShareAlike — CC BY-NC-SA license.

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Posted in code, How To, security, System Administration | Comments Off on Recovering from a WordPress hack

 
Better Tag Cloud