Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unfortunately, the person who is in charge of server maintaining is
away now and we can not get hold of him. Can any of you give me some
direction on how to track down the security hole and eliminate it
please?
IMO, in order to prove that the attacks are 'injection attacks', they need to provide something more than what you posted. By 'injection attacks', I'm going to assume they're talking about SQL injection (it could be something else, but I'm not seeing it in those logs you provided, and SQL injection involves taking advantage of possible permissions issues on webserver backend devices, which will most likely traverse over port 80).
The logs you provided appear to be normal traffic, that, BTW, is generating 403 errors, meaning the server understood the request but rejected it. That shows that the 'attacks' aren't getting through.
Now, some of the logs don't make sense to me. I also run a webserver that sees public traffic and my logs typically don't look like:
What's throwing me off is the "//.infohttp://http://" part of the logs you posted. Unless someone (or something, like a script) is actually entering that as part of the URL...maybe the injection part of it is after (but not logged) the "?" of the URL?
Another question is the "our.server.ip.address". Why would their own IP address be showing in their own web server logs. Maybe they're doing something with their server that I typically don't do, but I've never seen my own IP within my logs, unless I'm visiting my own pages from my home internet account.
You've got issues, because, if that's your site, I tried to traverse the directory (upward) and got as far as http://yscfortworth.org/calendar before I was redirected to a site indicating that your site was compromised. Your site has basically been tagged. I suggest you either conduct an investigation of how you may have been attacked. This is important, because you want to learn from this so that your site won't be compromised again soon after you wipe out and reinstall your system. I suggest NOT repairing your existing installed, as you may miss something crucial, leaving open a backdoor (there could be more than one).
Inaddition to what's been said already: please post say 20 or 30 consecutive lines that include offending ones from the log between BB code tags like this:
Code:
tac logfile | head -30 | sed "s|10.20.30.40|x.x.x.x|g" > outfile
Replace the "10.20.30.40" with the IP address of the server, don't scrub anything else and please don't use weird line breaks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.