I realize we’re not the first to write about this, but my intention is not to be a ground-breaking news source, but for our readers, I hope to be at least educational.
We’ve been seeing more log files, ever since we’ve been beta testing our new log analyzer, with probes for fckeditor and also editormonkey. This has led us on a journey to see why.
What we found was that many people are using editormonkey, even though it’s been “shelved” for some time. This means, no updates, nobody to fix bugs or more importantly – no security patches.
Here is a screenshot from the Editormonkey website:
For those of you unfamiliar with FCKeditor and Editormonkey, they work with various programs like WordPress, Joomla and other Content Management Systems (CMS), to provide a more robust writing platform.
These programs were designed to bring more text editing features to web based programs.
According to the CKEditor website:
The problem with any plugin, component, module, etc. is that they often times provide a file manager. A file manager for an editor is key so you can upload graphic files without leaving the editor. For instance, if you wanted to add a picture to something you’re writing about, you would upload it to your website and then insert into your text. A good editor will enable you to perform that task, without ever leaving the editor.
When you have multiple ways of uploading files to your website, you also introduce multiple exploits for hackers to abuse and infect your website.
Let’s see what is so bad about this.
First, let me begin by saying that if you follow our security principles, you’ll know that all software should be kept up-to-date.
Yes, that means even web based editors.
For older versions of FCKeditor, like 2.0 -> 2.2, this string is dangerous:
This allows an attacker to upload a file, like a backdoor shell script to the vulnerable website without any real “hacking” skills.
How would a hacker know you have this installed on your website?
Google is a hacker’s best friend. They can search using:
And find websites that Google has indexed and found that string.
What can you do to prevent this?
I’m glad you asked.
First, you can update your software. As posted above, FCKeditor has been renamed CKEditor. Update immediately.
Next, you can also use “security by obscurity”. In your robots.txt file you specify what the search engines index on your website. Does the world need to know what plugins you’re using in your WordPress blog?
You can use something like this in your robots.txt file:
# Hide certain folders from spiders
Disallow: /(path to your editor folder)
We’re not big fans of relying on security by obscurity so you should also locate the config.php file. It’s usually located here:
Open it with a text editor and search for the line that looks like:
$Config[‘Enabled’] = true ;
And change “true” to “false” (no quotes). That will disable that connector.
Other safety precautions you can take is to password protect the editor folder. Usually your hosting provider will have that option in their Control Panel for your account.
You could also delete the filemanager folder altogether. This eliminates the vulnerability completely.
If you absolutely have to upload files to your website via the editor, then I suggest you pick some area of your website to designate as an upload folder, but you should know that the permissions on that upload folder have to be set to 777 (world readable/writable). Again, you are warned not to do this.
In review, always use a multi-layered strategy for website security.
- Keep all software updated – even editors
- Hide folders from search engines
- Hide folders by using password protection
- Disable potentially vulnerable functions
- Hire a good security company (like us!)