If you visit www.chintee.com, the Reliance ADAG owned site, you’ll be able to save the php file serving the front page. And the php file includes the database connection details — with databasename, user id and the password.
This vulnerability is caused because of an apache web server config setting.
Wake up guys !! With 900K users on BigAdda and even more on Zapak, you cant afford to screw up like this.
13 Responses to “Configuration flaw on Chintee.com exposes database connection details”
what is the relation of the site with Zapak and BigAdda? Do all these use same DB server or what?
Wow, they haven’t fixed it yet. Good find!
balaji, all of them are from reliance..
however, I don’t think anything is lost yet. they could have disallowed internet access to the db. but it sure looks stupid..
it looks stupid, i have downloaded the file, looks like they are using the same db for bigadda also, Bigadda is based on Phpizabi, the db username shows that (Bigadda URls are similar to phpizabi). Not only the index file the other files also have the db details, see the polls file.
@ram,
I’m not sure if they have the same db for bigadda. It might be the possibility that they just named the db tables as bigadda_*…Remember that before bigadda was launched, it had a similar blog / comments section for selecting the logo..
To me, it smells like costly acquisitions in future
Here’s another one from Vodafone…
Just try this URL
http://ebp3.vodafone.in/mumbai/viewer/viewframeset.jsp?name=/MumbaiEBP/BC01/20071201/8.xxxxxxxx.00.00.xxxxxx.roi&userID=wssuser1&password=wssbill&checksum=xxxxxxxxxx
The portions with the ‘x’ character are my own details that I have blanked out no purpose.
As you notice the URL has details of the server user name and password.
This flaw is easily noticeable in the Firefox browser when you log in to check your bill details from Vodafone.
I raised a request with them to fix it - but apparently, no one is bothered
Cheers,
VodafoneUser
@mytechiedata
that happens when you use a GET method for submitting login forms instead of a POST.
GET methods should never be used on http requests while submitting a form.
miserable programming on their behalf.
@pranav
What is worse is that google caches the URL as well
Try searching for wssuser1 or wssbill
Thats sad. Imagine the hordes of users who are at risk.
The php page is giving out the production server database connection details !
This shows how pathetic the development quality is. Who the hell wants to store database connection information in each and every file? Can’t they store that in some configuration file and restritct the access.
Indian companies are running the race of Social Networks and can’t maintain the quality and integrity.
Its going to be the end user who has to suffer.
Ha ha ha! Good catch and they are still dozing it seems
On one side they are claiming of such huge user base and on the other nobody from their side cares if the production site is even working. Huh!
@debashish
I was hoping that someone would wake up at R-ADAG and correct the problem.
hopefully, they realize their db details have been exposed and at least change the db credentials later.