Communication with php pogram
Monday December 22nd 2014

Michal Čihař: Secure your phpMyAdmin





phpMyAdmin is quite popular software (to give some numbers let’s mention 10000 downloads daily on SourceForge.net or 122685 reports in Debian’s popcon) and as such is quite attractive target for various scripted attacks. If you run phpMyAdmin installation somewhere you should really make sure it is enough secured, so that these script kiddies don’t get through.

In past month I’ve looked at what kind of attacks are these guys trying and in all cases these are pretty old vulnerabilities, some of them fixed years ago. So the first thing you should do is to update. It is always good to run latest stable version, but in case you can not for whatever reason, try at least taking the most important fixes and using them.

In ideal world your distribution would do this job for you, but in case it did not, you can for example take patches from Debian, which is pretty good at taking our patches (surprisingly it is not much related to my involvement there). To check which patches they have applied you can use excellent patch-tracker tool, which exposes patches from all released packages.

To give you overview of which issues are mostly being attempted to exploit by script kiddies right now, here is the list:

  • PMASA-2010-3 – yes, more than two years old, but still unpatched in some places
  • PMASA-2011-5 – “only” half year old
  • PMASA-2011-6 – only useful together with wrongly configured PHP

If you have fixed these, you should be pretty safe for now, but follow our security announcements for possible future issues (you can use RSS feed or subscribe to news mailing list, where all security issues are announced as well).

However there are more things you can do to keep you safer:

  • remove setup directory from phpMyAdmin, you will probably not use it after initial setup
  • prevent access to libraries directory from browser, as it is not needed, supplied .htaccess file does this
  • properly choose authentication method – cookie is probably the best choice for shared hosting
  • in case you don’t want all MySQL users to be able to access phpMyAdmin, you can use AllowDeny rules to limit them
  • consider hiding phpMyAdmin behind authentication proxy, so that MySQL credenticals are not all users need to login

So these are the basic steps which will help you against possible compromise, I might return to some of these in more details in future posts.

Filed under:

Debian

English

Phpmyadmin

Suse

|

0 comments
|
Flattr this!

View full post on Planet phpMyAdmin

  • Share/Bookmark
Related Tags: , , ,

Leave a Comment

More from category

Madhura Jayaratne: phpMyAdmin work during tenth and eleventh weeks

internet advertising Here I am combining work done on two weeks since I was on leave for four days during the latter [Read More]

Madhura Jayaratne: Public Transportation Usage Analysis for City of Chicago

internet advertising As part of my BI course I’m taking for my part time MSc, I started working on an analysis on [Read More]

Madhura Jayaratne: phpMyAdmin work during the ninth week

internet advertising This was a four day week since I was on leave on 3rd Wednesday. During the week I was more engaged [Read More]

Michal Čihař: Weblate 2.1

internet advertising Weblate 2.1 has been released today. It comes with native Mercurial support, user interface [Read More]

Madhura Jayaratne: phpMyAdmin work during the eighth week

internet advertising As mentioned in my last blog post I started working on the token mismatch issue that we received a [Read More]

Twitter On Me

<p>Error: Twitter did not respond. Please wait a few minutes and refresh this page.</p>

Calendar

December 2014
M T W T F S S
« Nov    
1234567
891011121314
15161718192021
22232425262728
293031