Table of Contents

1. Challenge

   Getting Started in the Lab Environment

   Here are the initial instructions and explanation of the lab environment. Read this while your environment is busy creating itself from nothing. Yes, this violates physics; we know. How fun!

2. Challenge

   Emulation

   In this challenge, you will be provided with an environment containing a web application vulnerable to CVE-2022-34265. You will walk through the steps required to identify the SQL injection and build out a proof of concept to exploit the vulnerability.

3. Challenge

   Detection

   In this challenge, you will access and analyze the log files of the web application serving the application vulnerable to CVE-2022-34265. Due to the exploitation requirements of the vulnerability in the example lab environment, the SQL injection results in specific server response codes, which can be used to identify attempted and successful exploitation - and thereafter analyze the activities the attacker performed.

4. Challenge

   Protection

   In this challenge, the learner will examine and implement different mechanisms to protect against CVE-2022-34265. The formal and correct solution of upgrading the vulnerable software will be discussed, and an alternative method of using a web application firewall at the ingress edge will be demonstrated (which has defense in depth merits, for example in a large organization where patching is difficult, assets are unknown, or an immediate response to a new vulnerability is required).

5. Challenge

   The Last Challenge

   Welcome to the final challenge! This is your last chance to experiment in the environment. Clicking Finish Lab will end this little world that flittered into existence just for you.