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.
Looks like shellcode to me, but what is it doing. I've shut the server down for now because of the line "admin" appearing in the log entry, has it been compromised?
it isn't. The first line is the attempt of a client (presumably a bot) to establish an SSL connection to your server, which your server doesn't support and therefore misunderstands the code as an HTTP request. The second line is an attempt to exploit a bug in Linksys routers known as the HNAP1 bug.
Quote:
Originally Posted by coralfang
I've shut the server down for now because of the line "admin" appearing in the log entry, has it been compromised?
Shutting down the server is over-cautious here, IMHO. The server itself isn't affected; it correctly answers these two requests with a 400 and 404 status. If you have a Linksys router which may have that bug, however, I'd replace it immediately. On the other hand, if there was a router in your network which is affected, the request wouldn't get through to your server.
So it looks like this is annoying for you, but not really a problem.
Ok thanks for explaining. The server itself is just for personal use at the moment, so it's not like anyone will complain about downtime haha. I was alarmed by the "admin" string before the date in the entries immediately following the suspicious request, thinking it could be exploiting nginx, but after reading somewhere it apparently means they only requested admin as the login name for the page and didn't actually login/create an account.
I don't have a router affected by this so that's good to know.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.