lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <07b101cd3537$cd5efc00$681cf400$@com>
Date: Fri, 18 May 2012 15:50:04 -0500
From: "Adam Behnke" <adam@...osecinstitute.com>
To: <full-disclosure@...ts.grok.org.uk>
Subject: Checking out backdoor shells
A backdoor shell can be a PHP, ASP, JSP, etc. piece of code which can be
uploaded on a site to gain or retain access and some privileges on a
website. Once uploaded, it allows the attacker to execute commands through
the shell_exec () function, upload/delete/modify/download files from the web
server, and many more. For defacers, it allows them to navigate easily to
the directory of the public_html or /var/www and modify the index of the
page.
In this write-up, we will be talking about PHP backdoor shells, how they
work, how to detect them and remove them. Below is a simple PHP code that is
very popular and is scattered all over the web
(http://stackoverflow.com/questions/3115559/exploitable-php-functions;
http://shipcodex.blogspot.com/2012/01/simple-php-backdoor-shell.html). This
code allows an attacker to execute *nix commands. For the full write up at
InfoSec Institute, check here:
http://resources.infosecinstitute.com/checking-out-backdoor-shells/
Content of type "text/html" skipped
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists