WEBVTT

00:01.750 --> 00:09.640
Come back in this video lecture we will see cross-site scripting or were you grassers the penguin that

00:09.710 --> 00:13.540
pretty insect Landsat attack.

00:13.600 --> 00:21.700
And it's most popularly card as Access's so cross scripting what inanity is often found in a lot of

00:21.700 --> 00:32.690
obligacion especially where a user provides input receiving areas like search farms and farewelled farms.

00:32.930 --> 00:40.490
If they use supply input is actually being executed by the web application which means that web application

00:40.520 --> 00:42.660
is cross-site scripting will not have

00:47.740 --> 00:52.550
no user provides javascript code instead of providing a legitimate text.

00:54.690 --> 01:02.700
And if the javascript code is being executed by the location which means that web application is cross-site

01:02.700 --> 01:12.530
scripting whenever he can also be used and in order to streamline EULA cookies session is uneven.

01:12.720 --> 01:19.030
It can also lead to CSA for tags so cross-site scripting is off great as

01:22.010 --> 01:25.170
the first one is reflected crosshatch scripting.

01:25.550 --> 01:33.530
And the second one is Tor cross that tipping and third one is done based across scripting.

01:33.940 --> 01:37.350
Now lets talk about both of them in much more detail.

01:38.350 --> 01:45.610
Reflektor cross-site scripting is also called as non-persons turn crosshatch scripting because here

01:45.850 --> 01:54.010
the user input is not stored in the database which means if the user input is not stored in the database

01:54.790 --> 02:02.070
the response of the real application is only shown to the user who is actually injecting the javascript.

02:02.530 --> 02:11.710
Which means if we are injecting something in search bar or our gyroscope is being executed by that application

02:12.280 --> 02:20.230
which means the response of that Javascript can only be shown to us not anyone else because the input

02:20.230 --> 02:25.090
is not stored in the database and often found in the search bar.

02:27.370 --> 02:31.050
Now let's talk about stored process scripting.

02:31.370 --> 02:38.630
So Star-Crossed sidestepping as so-called as stored access and pusses and access.

02:38.720 --> 02:38.960
Why.

02:38.960 --> 02:42.760
Because the user input is Dorton database.

02:43.160 --> 02:50.930
And when the user input is stored in the database then they are just for example there is one comment

02:50.930 --> 02:59.480
section and we commented out a javascript query and in place of command we added javascript queries

02:59.600 --> 03:03.720
and we will click on submit anyone with a database.

03:03.740 --> 03:13.460
Then the jousted also being executed on that user which means the impact of store grassers the ping

03:13.490 --> 03:18.140
is much more than non-persistent crasser scripting.

03:18.140 --> 03:24.680
And then it can also lead to CSA for that.

03:24.700 --> 03:34.300
Now lets see that Donbass process Tripti numbers access access simply means crosshatch the penguin notability

03:34.480 --> 03:43.930
that appears in the no means document object model instead of part of the extremal in effect do and

03:43.930 --> 03:50.780
store classers scripting that as you can see they will never the payload in the response page but in

03:50.920 --> 03:58.330
don't base across or scripting their statements or scold and response of attack will be exactly the

03:58.330 --> 03:58.990
same.

04:00.730 --> 04:02.640
Thats out of our taxes.

04:02.920 --> 04:03.970
Thanks for watching.

04:03.970 --> 04:05.770
I'll see you in next class.
