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.

Comments

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

Jsunpack-n Tutorial (Analyzing Malicious Documents)

INSTALLATION: Required Dependencies(all these dependencies are present in jsunpack-n package in a folder named depend): 1) Build and install pynids (nids) from ./depends/pynids-0.6.1.tar.gz To compile pynids, you may need the following (ubuntu) packages: libpcap-dev pkg-config python-dev libgtk2.0-dev libnet1-dev         To install these package either use software center or command apt-get install PackageName     $ cd depends     $ tar xvfz pynids-0.6.1.tar.gz $ cd pynids-0.6.1/ directory $ python setup.py build $ sudo python setup.py install 2) Build SpiderMonkey 'js' from ./depends/js-1.8.0-rc1-src.tar.gz     This package has modifications to the spidermonkey source code; therefore, it is not recommended you use default smjs packages. (Details of the modifications are in INSTALL.spidermonkey.shellcode and INSTALL.spidermonkey, for historical purposes)     $ cd depends/     $ tar xvfz js-1.8.0-rc1-src.tar.gz     $ cd js-1.8.0-rc1-src     $ mak

SSI Injection Attack

SSIs are directives present on Web applications used to feed an HTML page with dynamic contents. They are similar to CGIs, except that SSIs are used to execute some actions before the current page is loaded or while the page is being visualized. In order to do so, the web server analyzes SSI before supplying the page to the user. The Server-Side Includes attack allows the exploitation of a web application by injecting scripts in HTML pages or executing arbitrary codes remotely. It can be exploited through manipulation of SSI in use in the application or force its use through user input fields. It is possible to check if the application is properly validating input fields data by inserting characters that are used in SSI directives, like:  Code: < ! # = / . " - > and [a-zA-Z0-9] Another way to discover if the application is vulnerable is to verify the presence of pages with extension .stm, .shtm and .shtml. However, the lack of these type of pages does not mean that th