Chapter 5 of 9 · EC-Council 312-50

Web Application Hacking

Web servers, web app attacks, APIs and web shells, and SQL injection with its countermeasures.

  • 8topics
  • 36 minfast track
  • 1diagrams and exhibits
  • 14%of the exam

Topics in this chapter

Take them in order, or jump to the one you need.

  1. 1Web Servers: Attacks, Methodology and Patch ManagementWeb server architecture, common web server attacks, the attack methodology, hardening countermeasures, and the patch management…4 min
  2. 2Web App Concepts, Threats and Hacking MethodologyWeb application architecture, HTTP basics, the OWASP Top 10 categories and the stages of the CEH web application hacking…4 min
  3. 3Footprinting Web Apps, Client-Side Controls and Authentication AttacksFootprint web infrastructure, analyze an app, see why client-side controls fail, and recognize attacks on login, recovery and…4 min
  4. 4Authorization, Access Control, Session, Injection and Logic AttacksRecognize attacks on authorization schemes, access controls, session management, injection and input validation, and application…5 min
  5. 5Shared Environments, Database Connectivity and Web Client AttacksHow shared hosting, database connection weaknesses and attacks on the web client (XSS, CSRF, clickjacking) work, and the…4 min
  6. 6Web Services, APIs, Webhooks, Web Shells and Web App SecurityAttacks on SOAP and REST web services, API and webhook risks, what a web shell is and how to find it, and the controls that…5 min
  7. 7SQL Injection Concepts, Types and MethodologyWhat SQL injection is, why it happens, the in-band, blind and out-of-band types, and the stages an attacker follows from…5 min
  8. 8SQL Injection Tools, Evasion and CountermeasuresSQL injection tools such as sqlmap, how attackers try to evade filters and WAFs, and the countermeasures that actually stop SQL…Diagram5 min

About this chapter

What this chapter covers

This chapter is 14% of the EC-Council CEH v13 312-50 exam. It covers hacking web servers, the stages of a web application attack, attacks on the surrounding services such as web services and APIs, how web applications are secured, and SQL injection in depth.

The exam uses single-answer multiple choice questions. Most ask you to recognize an attack from a short description, name the tool, or choose the countermeasure that fixes the root cause.

The chapter has 29 outline topics, grouped into eight pages. It stays at the level of concepts, tools and defenses and contains no exploit code.

How the topics fit together

The pages move from the server, to the application, to the data behind it.

Web serversattacks and patchingWeb applicationthreats and methodologyLogin, access and sessionsInjection, services and APIsSQL injectiondatabase layer
  • Web servers: misconfiguration and missing patches, countered by hardening and patch management.
  • Web apps: the OWASP Top 10 and a staged methodology from footprinting to attacking services.
  • Access: authentication, authorization and session flaws.
  • Injection and surroundings: shared environments, databases, the client, web services, APIs and web shells.
  • SQL injection: types, tools, evasion and the fix at the root.
Exam tip

When a question asks for the best fix, look for the answer that removes the root cause, such as server side checks or parameterized queries, over one that only filters symptoms.

How to use these pages

Each topic page has the same shape, so you can skim for what you need.

  • What it is: the idea in plain words.
  • How it works: the mechanism, with diagrams and example commands.
  • What to remember for the exam: the facts to memorize.
  • Common mistakes: the classic traps.
  • Check yourself: three questions to test your understanding.

Try to match each short scenario to its attack category before reading the answer. The exam often describes symptoms and asks for the attack name or the best fix.

Ready for more practice?

The full EC-Council 312-50 question bank has 1,000 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by EC-Council. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.