Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: Spamming other servers virus via apache, how did it get in, and how to get it out?

  1. #11
    Join Date
    Feb 2014
    Beans
    142

    Re: Spamming other servers virus via apache, how did it get in, and how to get it out

    just because there is no changed files between your backup and current website, doesn't necessarily mean the problem absolutely is outside of /var/www, but it probably is. I would think XSS and CSRF would show up in the apache logs, but those could be possible problems especially if you wrote the site yourself (it can be easy for 1 person to miss some mistakes), and they would not need to alter any file on the website. If it is outside /var/www, then its possible someone got in from an other open service, maybe ssh server is running, maybe someone had physical access to the machine, etc. Without more information is hard to tell. I tend to believe the problem probably lies in /var/www or in apache itself, though, because the problem is leaving entries in the apache.log file.
    python -c 'print hex(3 << ((1024/4)-2))[:-1]'
    python -c 'print hex((1 << (1024/4))-1)[:-1]'

  2. #12
    Join Date
    Mar 2015
    Beans
    7

    Re: Spamming other servers virus via apache, how did it get in, and how to get it out

    I do have a file upload form... shouldn't be able to do that, but maybe. I know why they are doing it, SEO back links.

    PS
    These are other people comments, not mine

  3. #13
    Join Date
    Feb 2014
    Beans
    142

    Re: Spamming other servers virus via apache, how did it get in, and how to get it out

    you might want to do a web search for 'file inclusion vulnerability' which might show you how it works, and how you might fix that problem if thats what you have.
    python -c 'print hex(3 << ((1024/4)-2))[:-1]'
    python -c 'print hex((1 << (1024/4))-1)[:-1]'

  4. #14
    Join Date
    Mar 2015
    Beans
    7

    Re: Spamming other servers virus via apache, how did it get in, and how to get it out

    In the end it was a messed up proxy pass to node... where it wasn't locked to a domain, and they could use it for whatever the felt like, like spamming for backlinks.

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •