Skip to main content

Snort:Intrusion Detection System


Snort is a lightweight intrusion detection system that can log packets coming across your network. This
program can be used on smaller networks but on larger ones, with Gigabit Ethernet, snort can become
unreliable. Snort doesn't require that you recompile your kernel or add any software or hardware to your
existing distribution but it does require that you have root privileges.


Now we'll take a look at some basic rules to see how they work. The basic format of a rule is as follows:
function protocol source_ip/mask source_port -> destination_ip/mask destination_port options
A rules file will contain many lines of rules and it can look a little complicated at first. Here’s an example.
# look for stealth port scans/sweeps
alert tcp any any -> $HOME_NET any (msg:"SYN FIN Scan"; flags: SF;)
alert tcp any any -> $HOME_NET any (msg:"FIN Scan"; flags: F;)
alert tcp any any -> $HOME_NET any (msg:"NULL Scan"; flags: 0;)
alert tcp any any -> $HOME_NET any (msg:"XMAS Scan"; flags: FPU;)
alert tcp any any -> $HOME_NET any (msg:"Full XMAS Scan"; flags: SRAFPU;)
alert tcp any any -> $HOME_NET any (msg:"URG Scan"; flags: U;)
alert tcp any any -> $HOME_NET any (msg:"URG FIN Scan"; flags: FU;)
alert tcp any any -> $HOME_NET any (msg:"PUSH FIN Scan"; flags: FP;)
alert tcp any any -> $HOME_NET any (msg:"URG PUSH Scan"; flags: PU;)
alert tcp any any -> $HOME_NET any (flags: A; ack: 0; msg:"NMAP TCP ping!";)
# IMAP buffer overflow
alert tcp any any -> $HOME_NET 143 (msg:"IMAP Buffer Overflow!"; content:"|E8C0FF FFFF|"; flags: PA;)
# x86 named buffer overflow
alert tcp any any -> $HOME_NET 53 (msg:"named Buffer Overflow!"; content:"|CD80E8D7 FFFF FF|"; flags: PA;)

Now lets try to make our own rule and test it out....

Step1: Making rule:


Step2: Now run snort with this rule and try to telnet to this machine to generate alert messages.





You can use many options with snort to get better console display.To check out other option just type snort --help in terminal.

Output:
check out the log directory which we have defined with -l option.


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