TRANSCRIPTEnglish

Web Investigation Lab

22m 35s2,608 words438 segmentsEnglish

FULL TRANSCRIPT

0:00

I hope everyone is doing great. So today

0:02

we have a quick lab by cyber defenders

0:05

which called the web investigation lab

0:08

and this lab is really good to test your

0:10

you know network forensics skills and

0:13

the usage of tools like wire sharkark

0:15

and network miner. So let's start by

0:18

reading the scenario and answering the

0:20

questions. So the scenario says you're a

0:24

cyber security analyst working in the

0:26

security operation center of a book

0:29

world an expansive online bookstore you

0:31

owned for his vast selective literature.

0:35

Bookw world pride itself of providing

0:36

seamless and secure shopping experience

0:38

for book enthusiasts around the globe.

0:40

So recently you have been tasked with

0:43

reinforcing the company's cyber security

0:45

posture, monitoring network traffic and

0:47

ensuring their digital environment

0:49

remains safe from threats. So late one

0:52

evening an automated alert is triggered

0:55

you know from the same tool maybe by an

0:58

unusual spike in database queries and

1:00

server resource usage indicating

1:03

potential malicious activity. This

1:05

anomaly raises concerns about the

1:07

integrity of the book, book walls,

1:10

customer data, internet systems,

1:12

prompting an immediate and thorough

1:15

investigation. As the lead analyst in

1:17

this case, you are required to analyze

1:19

the network traffic to uncover the

1:21

nature of the suspicious activity. The

1:24

objective include identifying the

1:26

attacker vector, assessing the scope of

1:28

any potential data breach and

1:30

determining if the attacker gain further

1:32

access to the bookwor

1:34

systems. All right. So you can download

1:37

the pickup file uh from here and you

1:41

you'll be provided by the password here

1:43

cyber defenses.org. I already downloaded

1:45

it. You need to unzip it.

1:51

As you can see, this is the pickup file.

1:55

So, okay, we'll close this one and start

1:57

by answering the questions. So, question

2:00

number one says, by knowing the

2:02

attacker's IP, we can analyze all the

2:04

logs and actions related to the IP and

2:07

determine the extent of the attack,

2:09

duration of the attack, and the

2:10

technique used. Can you provide the

2:12

attacker's IP? All right. So, normally

2:15

what we do when we analyze uh pickup

2:18

files, we look at the conversations,

2:20

right? So we have here around 88,000

2:24

packets. So we can go to statistics

2:26

conversation IPv4 and you know to find

2:30

the attacker normally um we can look for

2:33

the most sent packets right so here we

2:36

can see 88 packets exchange between this

2:40

IP and this IP one of them of course

2:43

will be our server or the bookstore

2:45

server. So let's you know it says from

2:48

this IP A to B there's around 44,000

2:52

packet and 7 mgaby of data and B2A we

2:55

have around 21 megabyte of data. So just

2:58

let's filter by

3:02

select A to B

3:05

and as you can see here

3:09

this is the communication you can see uh

3:13

you can see here for example

3:16

send send packet and then it responded

3:19

responded act this means this IP

3:21

responded with synak okay send send

3:27

you Well, there's some lot of sin

3:30

packets. Okay. So, what we can also do,

3:33

we can filter by sin flags, right? So,

3:36

TCP

3:38

flags.

3:39

Okay. That's Yeah, this is the filter.

3:42

So, we're filtering for sin of one and

3:46

an an acknowledgement of zero to filter,

3:48

you know, uh if there's was any

3:51

suspicious reconnaissance activity or

3:53

scanning activity related to sin

3:55

scanning. So if we filter by that as you

3:58

can see that this IP 101 224 2512 131 is

4:04

sending a lot of uh syn packets

4:06

consecutively to this IP. So let's

4:10

follow you know just follow TCP stream

4:13

and as you can see here

4:18

okay nothing provided wait

4:23

okay just uh

4:26

let's just uh yep

4:29

again

4:31

so you can see this is the

4:34

this is the flags 111 273 okay what you

4:37

can do just follow TCP stream. All

4:40

right. So, as you can see here,

4:44

um, here's suspicious user agent which

4:47

is used for SQL injection. Let's see

4:50

trying to get search.php.

4:53

All right. So, just to confirm our our

4:57

thoughts what we can do just come to a

5:00

random packet and look follow the TCP

5:03

stream.

5:05

Okay. As you can see here the user agent

5:08

of the of the this IP is of this IP 111

5:13

is SQL map. So for those who don't know

5:16

SQL map is an a tool used you know in

5:19

SQL injection attacks which is really

5:22

famous attack.

5:24

Okay. And you can see here the host is

5:26

bookworld store. All right. So this host

5:28

this is our uh company

5:32

uh server and this is the attacker's IP.

5:34

So the answer will be indeed this

5:41

uh IP. Let's just copy it.

5:46

Yeah. So it will be 111.224

5:51

11.224.250

6:01

131.

6:03

All right. Perfect. So question number

6:05

two says, if if the geographical origin

6:08

of an IP is known to be from a region

6:10

that has no business or expected traffic

6:13

with our network, this can be an

6:15

indicator of targeted attack. Can you

6:17

determine the region city of the

6:19

attacker? All right, we can just you

6:21

know use some threatel platforms like

6:23

abuse IP maybe geo

6:28

geol location

6:31

IP or IP lookup. These are all good wip

6:34

uh you know ser all good sites.

6:38

We can just paste the IP here.

6:53

Okay, it's just loading. Okay. So as you

6:56

can see it says the IP belongs to China

7:01

from a region called Hibby and the city

7:04

called Shaz Hung. Okay. So this must be

7:08

the answer.

7:11

Okay. So here

7:14

just copy

7:16

close this one. And indeed

7:21

it's the answer. All right. Let's close

7:24

this one.

7:25

Question number three says, "Identifying

7:27

the exploited scripts allow security

7:30

teams to understand exactly which

7:32

vulnerability was used

7:35

in the attack. The knowledge of critical

7:37

finding appropriate patch on work around

7:39

close activity and prevent future

7:41

exploit. Can I provide the vulnerable

7:42

PHP script name? All right. So as you

7:46

may have noticed, we found some

7:48

suspicious PHP scripts. So what we can

7:51

do here? We can filter for frame

7:55

contains

7:57

PHP

8:00

you know and look for some PHP you know

8:04

search as you can see we have about

8:06

style contact nothing suspicious you can

8:10

contact search okay as you can see here

8:13

this search php you can see some

8:16

suspicious encoded like commands or

8:19

injection as you can see here select

8:22

So this is like it's trying to select

8:25

from a table in the database which is

8:27

like famously like used in SQL injection

8:31

attacks. You can see here um

8:36

wait for delay. This is time based SQL

8:38

injection. Yeah. So yeah. So this this

8:43

all is related to SQL injection. So the

8:45

vulnerable PHP field is actually this

8:48

one search.php. So just if you follow

8:51

the TCP stream as you can see the

8:54

request was accepted as you can see the

8:56

host accepted it's not like server

8:59

error. So so this is the parameter that

9:02

has been uh you know abused and this is

9:05

the PHP search php. So you can see here

9:10

search dotphp

9:14

correct right. Question number five says

9:17

can you provide the complete request URL

9:19

that was used to read the web server

9:21

available databases. All right so we

9:24

have already found um the the first

9:27

abused SQL injection the search.php. So

9:30

for for for this uh question for this

9:33

question we can use the same approach

9:35

which is to filter the h the frame that

9:39

contains PHP and look for anything

9:42

related to databases right. So

9:47

okay we have started here you know uh

9:52

the first PHP script was this is the

9:54

first SQL injunction attempt in the

9:56

search.php.

9:58

So we want something related to uh you

10:02

know database here table name. Okay you

10:06

can see select where book okay so we

10:12

want something that's related because

10:13

usually in SQL injection the attack is

10:16

trying to dump database from the website

10:19

or the web application. So this could

10:22

include you know something related to um

10:25

you know information schema. So if you

10:29

if you're not familiar maybe if you do

10:30

an SQL injection attempt you'll have a

10:34

better understanding. So here for

10:36

example you can see selection

10:39

select go calculate union. Okay.

10:44

Okay. Union.

10:46

So okay union. Okay. You can see here

10:51

something to from select from union. All

10:55

right. So there's actually a lot of uh

11:00

you know options but we want something

11:02

related to databases like uh info we

11:05

have schema name information schema

11:08

data.

11:10

Okay

11:13

concatenate

11:15

search name array concate. So all right

11:18

so you can see that this user is trying

11:21

to look for something related to can see

11:24

here table name. So here he access the

11:27

table here column here the password

11:31

username here the table fields here the

11:34

column here the table name so this is

11:36

the information schema which might be

11:38

related to the database we can just

11:40

follow the TCB stream

11:45

and then copy this one from here to here

11:49

and decode it.

11:52

All right. Uh,

11:54

cyer

11:57

chief.

11:59

Sorry.

12:00

Chief.

12:06

All right. Okay. Cyber chief

12:11

URL

12:13

decode. All right. So, we have already

12:15

decoded it. So, this is the decoded

12:19

version.

12:21

Copy and go to cyber defenders.

12:26

Paste it.

12:29

All right. Luckily, it's the answer. So,

12:32

question number six says, assessing the

12:34

impact of the breach of the data access

12:37

is crucial, including the potential harm

12:39

to organization reputation. What's the

12:41

table name containing the website's

12:44

users data? Right. So as you may have

12:46

seen we found some interesting table

12:50

colments. Uh just let's return to the

12:54

let's return to the frame contains PHP

12:59

we found something related to users if

13:03

you have noticed columns.

13:06

Yeah. So as you can see here this is the

13:09

information schema the schema and here

13:12

the table name. Okay. So they're looking

13:15

for table related to user information.

13:18

So here column type. Okay. We have

13:22

something here called uh password

13:26

username.

13:27

All right.

13:29

Admin. We have also here a table name.

13:33

Table name. All right. We have table

13:36

schema table name. We have also here

13:39

something interesting. You can see email

13:42

first name. Okay. C phone. So this might

13:46

this might be related to user

13:48

information, right? So follow TCP

13:50

stream. So yes. So this is trying to

13:55

okay

13:57

look for the email column, the first

14:01

name, last name and the phone number and

14:05

from the book world database customer.

14:08

So as you can see even from the

14:10

highlighted we can guess it it is most

14:13

probably the customer's table.

14:18

So yeah

14:22

so it's the answer indeed. Question

14:24

number seven says the website

14:26

directories hidden from the public could

14:29

serve an authorized access point or

14:31

contain sit functionality not intended

14:34

for public access. It's going to provide

14:36

the name of the directory discovered by

14:38

attackers. Yeah. So what attackers

14:39

normally do that they try to find for

14:42

hidden pages you know that let's say

14:45

admins or uh websites owners try to

14:49

access to login right so what we can

14:52

look for we can see look for HTTP

14:55

request

14:58

no rel yeah HTTP request method related

15:02

to post. So,

15:06

and we filter.

15:09

So, it's not working.

15:14

All right. So, as you can see here, this

15:16

is the attacker's IP. This is the

15:18

server. He accessed a portal or a page

15:23

called admin/lo.php.

15:25

So we can just follow CP stream

15:29

and as you can see yeah he indeed

15:33

accessed this admin.lophp

15:38

admin login.php.

15:41

Yeah. So this is the answer. And here

15:43

you can see he supplied the username

15:45

admin and the password admin. So yeah.

15:48

So since they're asking for the

15:50

directory this is the answer.

15:54

We'll just

16:00

Okay. So,

16:04

all right.

16:06

Coming to question number eight says,

16:07

"Knowing which credential were used

16:09

allow us to determine the extent of the

16:11

account compromise. What are the

16:14

credential used by the attacker after

16:16

logging in?" All right. So after he

16:18

logged in uh so we have one of the

16:21

packet we already seen the TCP stream of

16:23

it as you can see this is the directory

16:26

he accessed admin all right and you can

16:30

see he here he he submitted admin and

16:34

the password admin however if you look

16:36

at here we cannot supply admin admin so

16:41

this means that after he logged in he

16:44

supplied another password so what What

16:47

we can do is just look for the for the

16:50

same post requests to the admin

16:53

directory which is

16:57

um HTTP request method post. All right.

17:02

Okay. We analyze the first one. Let's

17:04

look at the second packet. Okay. Follow

17:09

TCB stream. And as you can see here, it

17:13

says also the same admin login. We know

17:16

that the first username was admin admin

17:17

but here we have admin and the password

17:20

called change me accepted. So let's look

17:25

at it.

17:28

Admin

17:30

change me.

17:34

All right. So says admin change me.

17:40

All right. So c h a n g e. All right. So

17:44

this is not also the password.

17:47

Uh just let me copy it. So

17:52

just in case.

17:59

All right. So this is not the answer.

18:01

Let's look for another packets related

18:04

to the credentials.

18:07

All right. We analyze the first two.

18:09

Let's look at this one. follow TCP

18:13

stream.

18:15

Okay. The same thing admin password

18:18

change me.

18:20

Okay. So again we'll use the we analyze

18:26

the fourth packet. Analyze this one and

18:29

let's look at this one. Followp

18:32

stream. Okay. Here we have another

18:36

username and password here. Admin and

18:38

password.

18:40

uh admin 1 to three. So let's let's try

18:44

this one

18:47

here. Admin

18:49

and the password

18:51

admin 1 2 3.

18:54

Oh, still

18:57

okay.

19:03

All right. So still it's not the answer.

19:08

All right. Uh

19:10

let's look at the last packet.

19:13

The last bucket provided.

19:18

Okay. Here

19:20

follow TCP stream. Okay. In this one as

19:24

you can see here there's no credential

19:27

uh submitted but we we can see a file

19:30

name called nv.php.

19:34

So he uploaded file name. However, we're

19:36

looking for credentials right. So

19:40

uh just let's me try uh might be an

19:44

admin

19:46

and then

19:48

admin one to three. All right. So

19:53

change me the first one.

19:57

Change me.

20:00

All right. Maybe

20:02

see change.

20:05

All right. So for some reason um cannot

20:10

find the password here even though it's

20:12

this the one submitted.

20:14

Um let me analyze it again. Admin.

20:19

Okay. So let's look at this one for

20:22

instance.

20:26

Uh sorry.

20:29

Okay. Let's look at

20:32

admin. Admin.

20:34

Admin. admin.

20:37

Okay,

20:42

for this one we have admin and change

20:46

me. C H N G E me. So I tried it but

20:50

still

20:58

all right that's credential.

21:00

All right. So

21:05

change me. All right. So this packet the

21:08

password is

21:10

username default. Here is

21:15

change me. Admin. Okay. Here is admin.

21:19

Yeah. Okay. We have here admin. Okay.

21:22

Admin 1 to three with this hash. Okay.

21:25

That's why. So admin and admin 1 2 3

21:28

with this exclamation mark. So my bad,

21:32

my bad, my bad, my bad. Admin one, two,

21:35

three and exclamation.

21:38

All right, this is the correct answer.

21:40

So

21:42

last question says, we need to determine

21:44

if the attacker gained further access to

21:45

control of our website. What's the name

21:47

of the malicious script uploaded by the

21:50

attacker? So we already found this one

21:52

actually and the malicious script

21:54

uploaded by the attacker can be traced

21:58

by looking here at the last packet

22:00

related to the post request

22:03

of just followed TCP stream. We can see

22:06

here a file name called NVR.php.

22:11

Yeah. So this is uploaded as you can see

22:14

the host the server accepted the

22:17

request. So yeah. So hopefully this is

22:20

the answer.

22:23

All right. So nice. We solved the lab.

22:26

Hope you enjoyed this video just, you

22:28

know, for the sake of practice. And

22:31

yeah, see you in the next

UNLOCK MORE

Sign up free to access premium features

INTERACTIVE VIEWER

Watch the video with synced subtitles, adjustable overlay, and full playback control.

SIGN UP FREE TO UNLOCK

AI SUMMARY

Get an instant AI-generated summary of the video content, key points, and takeaways.

SIGN UP FREE TO UNLOCK

TRANSLATE

Translate the transcript to 100+ languages with one click. Download in any format.

SIGN UP FREE TO UNLOCK

MIND MAP

Visualize the transcript as an interactive mind map. Understand structure at a glance.

SIGN UP FREE TO UNLOCK

CHAT WITH TRANSCRIPT

Ask questions about the video content. Get answers powered by AI directly from the transcript.

SIGN UP FREE TO UNLOCK

GET MORE FROM YOUR TRANSCRIPTS

Sign up for free and unlock interactive viewer, AI summaries, translations, mind maps, and more. No credit card required.