Buffer Overflows PDF
Buffer Overflows PDF
– Attackers use buffer overflows to corrupt the execution stack of a web application:
- By sending carefully crafted input to a web application, an attacker can cause the web application to
execute arbitrary code effectively taking over the machine.
- Buffer overflow flaws can be present in both the web server or application server products that serve the
static and dynamic aspects of the site, or the web application itself.
- When web applications use libraries, such as a graphics library to generate images, they open
themselves to potential buffer overflow attacks.
- Buffer overflows can also be found in custom web application code, and may even be more likely given
the lack of scrutiny that web applications typically go through.
- Buffer overflow flaws in custom web applications are less likely to be detected because there will
normally be far fewer hackers trying to find and exploit such flaws in a specific application.
WebGoat
The WebGoat, as a deliberately insecure web application, which is aimed at helping developers learn about
security vulnerabilities first hand by hacking the WebGoat.
It includes numerous exercises for topics ranging from Injection Flaws, over Cross-Site Scripting (XSS) to
Denial of Service and many others.
This will start a Webserver on port 8080. You can access it via http://localhost:8080/WebGoat/
Login
WebGoat
- Once the web form is filled, a Price Plan is offered to be accepted by the guest:
- Entering 4097 characters all the hidden fields are revealed, containing the hard coded information related to
the VIP guests:
As we use web developer addon to view the weakness in form,
If we use 4097 characters in room number and press submit button then we can get multiple entries
to see the details. This is the method to get the data leakage.
- The challenge of the exercise is to reveal information and data about VIP guests, by taking
advantage of the Buffer Overflow vulnerability suffered by the application.
- The strategy is to test various character strings with different lengths (1025, 2049, 4097, ..) until you
find the one that causes the buffer overflow and therefore the disclosure of confidential information
stored by the vulnerable application.