Skip to main content

Source Routing Demystified

As in my last post i have already make it clear about source routing and its type.Now lets do some practical  to understand it more clearly.Below given figure shows lab environment on which i ll be doing ping using different options.

Loose Source and Record Route 
Loose Source and Record Route

Strict Source and Record Route
Strict Source and Record Route
"ping -j" option is used for loose source routing and "ping -k" for strict source routing.Now what we did here we used same paths for loose and source in first case then differ it slightly to understand the difference.
Now when we used the same and correct path which have all hops between source and destination then both loose and strict routing shows the same result. 

 Difference Between Loose and Strict Routing

Now what we did here we remove the gateway from the path list which we are using .so what happened loose source routing showing result instead one hop or the very first hop is missing but strict routing showing request timeout error because 46.1 was its gateway and without reaching gateway it would be impossible to reach the 45.1 directly.
So actually in loose source routing even if you put a few IP or Ip that are not in order then also packet  will continue its journey till it find those path.But in case of strict source routing it is required that you put all the  hop ip address which are in between source and destination ,if anyone of them is missing or not in order as specified then packet will die in transit.


Popular posts from this blog

Hacking Windows 10 UWP App: DLL Injection & common Vulnerabilities

I recently started working on  widows 10 Apps( Apps not Applications) security. Before diving deep in hacking terms lets try to understand what's new in Windows 10 UWP( Universal Platform) as compared to old Apps. Lets begin with how apps actually work on windows 10(desktop/tablet). Now windows 10 comes with a container only for running apps inside the isolated environment. By default, /APPCONTAINER(Linker Flag) is off. This option modifies an executable to indicate whether the app must be run in the appcontainer process-isolation environment. Specify /APPCONTAINER for an app that must run in the appcontainer environment—for example, a Windows Store app. (The option is set automatically in Visual Studio when you create a Windows Store app from a template.) For a desktop app, specify /APPCONTAINER:NO or just omit the option. The /APPCONTAINER option was introduced in Windows 8. Now there is no registry entry concept for these app in the System HIVE rather they install they own hiv

Animated Cursor Vulnerability

Step1: create two file on attacker side 1) default index.html and 2) cursor file to load Now save the proof of concept in a txt file(cursor.txt). use above command to cut down the hex part from proof of concept and paste it in buffer.ani Step2 :upload the above two files in your apache webserver.  Step3: Try to open index.html from window-xp and analyse the behavior of IE using ollydgb in order to find the offset address where EIP will get over written. Attach IE in ollydgb and put malicious url in it. As we can see now that EIP is overwritten with 42424242 that means this place is our offset. Now we will put the address of jump instruction in place of 42424242 which we will get from user32.dll by searching for command JUMP DWORD [EBX],now we jumped at ebx because it contain the malicious .ani file address. Just go into view=>executable=>user32.dll , press enter. Now try to find a jump [ebx] instruction in user32.dll by pressing ctrl

Assignment 01(Enroll TO Offensive-Security Course)

Steps 1:download the page. 2:open fc4.js in your favourite editor and add following lines in it or just replace it with vode given below. 3:then open the download html file in browser and fill the form with your email and a garbage value string. 4:thats it? it will show you the real security string?? yeah but  ...theirs another challenge waiting for you ... :D function fc4me(srvstr) {    if(! || !document.pleazfc4me.securitystring.value) {       alert("Please fill in all the required fields!");       return false;    }    else {       document.pleazfc4me.submit();     }    var t=hexMD5("\x74\x72\x79\x68\x61\x72\x64\x65\x72"+srvstr) alert(t) document.write(t) } Finally Got In :-)