Tag Info

Hot answers tagged

6

You are being hit with Shellshock attempts. As long as you have patched your bash, you should be safe against these attempts. However, you might want to invest in a system for banning repeat system abusers. Try fail2ban. What is a specific example of how the Shellshock Bash bug could be exploited? If you haven't patched bash, you are in big, big trouble. ...


3

It's very hard to be have assurance there is no malware present on your server. There are indicators of compromise, but considering you probably didn't log anything remotely and did not have controls in place to prevent unauthorized alteration, it's very hard to rely on your system. Some recommendations (from the perspective that you are on a very limited ...


2

Im unsure if this is the "correct" approach, but I would change the permissions of the file to owned by root but also owned by another group which only has read access. Making sure your upstart user is in this shared group. # groupadd upstart # usermod -G upstart the_user # chown root:upstart the_file.conf # chmod 740 the_file.conf The above adds a new ...


2

It should be safe to click (although I still wouldn't). It looks like the attacker tried to exploit the shellshock vulnerability. If your server is vulnerable, the script will already be executed, you calling it again doesn't add that much harm (in this case, you don't have any more rights than the attacker has, assuming you are not viewing the log from ...


1

Here 6 key steps : 1 - Secure your application code 2 - disable all modules not used. Try to disable all, and then, one by one, add modules. 3 - remove all scripts and backup files in the web folder. 4 - disable directory listing 5 - use modsecurity to protect your application from application-level attacks. 6 - Use Fail2ban to trigger HTTP errors ...


1

You dont have much to worry about regarding having your VM hijacked to attack the host of all the possible attacks thats really near the bottom of the list. Your outline above is pretty solid and would deter the majority of attackers (barring bots who will just hammer your system). If you want to throw an ips on there, check out snort (its fantastic). In ...


1

This is mainly an addition to armani's answer. As Win98 has not been maintained for years, you cannot expect the OS TCP/IP stack to be exempt of bugs. But you certainly can find a recent (decent) OS accepting to run on an old computer. NanoBSD for example declares that it can be customized to low requirements : it is possible to cut the system down, so it ...



Only top voted, non community-wiki answers of a minimum length are eligible