Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is damn vulnerable. Its main goals are to be light weight, easy to use and full of vulnerabilities to exploit. Used to learn or teach the art of web application security.
Vulnerabilities
- SQL Injection
- XSS (Cross Site Scripting)
- LFI (Local File Inclusion)
- RFI (Remote File Inclusion)
- Command Execution
- Upload Script
- Login Brute Force
Changes
- Added Acunetix scan report.
- All links use http://hiderefer.com to hide referrer header.
- Updated/added ‘more info’ links.
- Moved change log info to CHANGELOG.txt.
- Fixed the exec.php UTF-8 output.
- Moved Help/View source buttons to footer.
- Fixed phpInfo bug.
- Made DVWA IE friendly.
- Fixed html bugs.
- Improved README.txt and fixed typos.
- Made SQL injection possible in sqli_med.php.
WARNING
It should come as no shock..but this application is damn vulnerable! Do not upload it to your hosting provider’s public html folder or any working web server as it will be hacked. It’s recommend that you download and install XAMP onto a local machine inside your LAN which is used solely for testing.
You can download DVWA 1.0.4 here:
Or read more here.
Subscribe to Darknet RSS Feed Stored in: Exploits/Vulnerabilities, Programming, Web Hacking
Related Posts:
- Damn Vulnerable Linux – DVL – IT-Security Attack and Defense
- MultiISO LiveDVD v1.0 – BackTrack, Knoppix & Ophcrack
- Katana v1 (Kyuzo) – Portable Multi-Boot Security Suite
- Call for Authors and New Members for Relaunch of Darknet
- Phrack 64 Released – It’s been a long time..
- New Firefox vulnerability – DoS and [DELETED] – UPDATED
| 8,356 views |
lol… It’s vulnerable for expert like you but not beginners like me :p
Lol, those are all very old exploits,
brute force, since computers came out
command execution, who doesn’t know to use ; then command
file inclusion, does anyone really use this? Page=/etc/passwd comeon now
sql injection- old hat, only caused by programmers who don’t know what they are doing. They have a whole escaping system just for sanitizing inputs.
upload- yeah upload your own shell to run remote commands, i think
would work just fine
xss – inject code into the page, what is your name? bob<javascript blah blah blah send cookie to website blah blah blah
can be done with javascript: from address bar by rewritting variables.
lets see stuff mroe like buffer overflows, snmp traps, hping, nmap. Not more or less script kiddy stuff.
Lets see gdb
@Jeff Price
“Lol, those are all very old exploits,
brute force, since computers came out
command execution, who doesn’t know to use ; then command
file inclusion, does anyone really use this? Page=/etc/passwd comeon now”
Please keep in mind that dvwa is for teaching/learning.
“sql injection- old hat, only caused by programmers who don’t know what they are doing. They have a whole escaping system just for sanitizing inputs.”
SQL Injection is still a very real problem on the internet today, with most if not all of the big names being one time or another vulnerable. i.e. microsoft.com, nasa.com, ebay.com, etc…
It could be compared to buffer overflows. Buffer overflows have been around for many many years however they still exist and are still a major problem for big companies. i.e. MS, GNU Linux, Mozilla, etc…
“lets see stuff mroe like buffer overflows, snmp traps, hping, nmap. Not more or less script kiddy stuff.”
Implementing buffer overflows into the web application would be difficult as Apache and most other web servers already restrict the buffers on all inputs by default.
“it striped out the php code i placed between i think and would work just fine, if you need it email me at staxjp\ \[ @ \] gmail.com”
Could you clarify this?
Thanks to everyone for their interest. If you would like to try the next version before it has been released: https://dvwa.svn.sourceforge.net/svnroot/dvwa
Ryan
@Ryan, the first post I put I has put an example php shell, simple just using get [ 'cmd' ] and then using the system command, used for the file upload section so site would be host/uploaded/cmd.php?cmd=ls
Now that I read back on it I sounded mean. I acctually wish I had something like this when I started out. Good Job. I will give a new version a try.
Buffer overflows, now just for web services, rpc services, smtp, and yes apache still has the occasional buffer overflow in the server itself.
It is still surprising how many sql injections there still are. new releases of php stop them be default without using the escaping function.
If anything, it opens peoples eyes alittle more to what vulnerabilities really are.
@jeffprice…,
read the the goddamn name… it’s written “DAMN” vuln… off course it’s really vuln… if you know something about nmap, buffer overflow, bla..bla… then why you don’t write your godDAMN own…
It seem you are kiddie that act like an expert… haha… sorry
Just a quick update to let everyone know that DVWA has a new home and that we will be releasing the new shiny version (1.0.5) soon!
http://www.dvwa.co.uk/
@Jeff dude saying that LFI isn’t a valid method for web app hacking shows your ignorance. LFI can be used to poison Apache logs and allow the hacker RCE. As for putting BoFs in web apps, it really is quite impossible. If you want to hack the backend though, please, go ahead and enlighten us with your skills by finding the Apache 0day or the litespeed http 0day