Affichage des articles dont le libellé est OWASP. Afficher tous les articles
Affichage des articles dont le libellé est OWASP. Afficher tous les articles

OWTF: OWASP Offensive Web Testing Framework

OWTF is OWASP’s (Open Web Application Security Project) Offensive Web Testing Framework. This tool automates the manual and un-creative part of pen-testing. OWASP’s project OWTF is focused on penetration testing efficiency and alignment of security testing standards.

This framework will help pen-testers to:

1) View big picture and think out of the box.
2) More efficiently find and verify vulnerabilities.
3) Due to automation, gets more time to work on complex vulnerabilities.
4) Perform more fuzzing on apparently risky parts.

The tool is highly user friendly and can be used by anyone without developing skills. Although, understanding and experience will be required to further investigate and use the output.

Features

Resilience

It allows OWTF to store partial output when a tool crashes. It will store the output and allow pen-tester to monitor processes.

Flexibility 

It allows pausing the processes when network connection of host or victim goes down. You can resume them later, avoiding loosing data.

Easy to Use API

OWTF uses PostgreSQl on back-end, enabling pen-testers to handle all functions and options through APIs. Pen-tester can add new feature with less efforts.

OWTF supports many popular pen testing standards making it considerable by pen-testers and ethical hackers. Its responsive interface enable user to easily work on it without developing skills.

Prerequisites

There are few packages which are mandatory before you proceed
• Git client: sudo apt-get install git
• Python 2.7, installed by default in most systems
• Wget: sudo apt-get install wget

Manual installation of OWTF is nothing but cloning the repository and running the install script
git clone https://github.com/owtf/owtf.git



~ samedi 18 juin 2016 0 commentaires

OWASP NINJA PingU - Not Just A Ping Utility


http://www.ehacking.net/2014/06/owasp-ninja-pingu-not-just-ping-utility.html
NINJA-PingU Is Not Just a Ping Utility is a free open-source high performance network scanner tool for large scale analysis. It has been designed with performance as its primary goal and developed as a framework to allow easy plugin creation. It comes out of the box with a set of plugins for services analysis embedded devices identification and to spot backdoors.




How NINJA PingU Works?

NINJA PingU takes advantage of raw sockets to reduce the three-way TCP handshake latency and it's state. Directly sending IP packets also avoids the TCP stack overhead.



It also implements non-blocking networking I/O in the plugin's interface by means of epoll. Each component is multithreaded and they have built-in caches to minimize synchronization points. In addition, the results persistment operations are buffered to reduce disk writes.

Why NINJA PingU?

It has been developed to easily allow developers build their custom plugins. Samples of those can be found in its codebase. NINJA PingU also integrates gnuplot to automatically plot the analysis results. In addition, a custom terminator has been embedded for enhanced data visualization.

NINJA PingU V1.0 is available here.  


Requirements

NINJA PingU comes with all the necessesary dependencies out of the box. The following platform is requiered, though.
- gcc
- Linux box. Will not work neither on *BSD or Windows OS.
- Root Privileges



note: root is required to create raw socket descriptors.

Getting Started

NINJA-PingU currently, only works under Linux and the gcc compiler is required. To get pingu, you can run:
$ cd /tmp; wget https://github.com/OWASP/NINJA-PingU/archive/v1.0.1.tar.gz; tar -xvf v1.0.1.tar.gz; cd NINJA-PingU-1.0.1/; ./npingu.sh

The Makefile will build the binary bin/npingu and the ninja-pingu plugins located at src/plugin. On the other hand, you can run the npingu.sh script, which automatically compiles NINJA PingU, tunes the operating system for enhanced network performance, and launches a custom terminator terminal for improved user experience.
$ ./npingu.sh

Basic Usage

The following is the NINJA PingU basic usage.
# sudo ./bin/npingu [OPTIONS] targets
-t Number of sender threads.
-p Port scan range. For instance, 80 or 20-80.
-d Delay between packages sent (in usecs).
-s No service discoverage (less bandwith load, more hosts/time).
-m Module to run. For instance, Service.
[targets] Can be a single ip or a range (i.e. 0.0.0.0-255.0.0.0).
-h Show this help.

Below it is shown some examples.
# ./bin/npingu -t 3 -p 20-80 188.165.1.1-188.255.1.1 -d 10 -m Service
-Targeted Hosts [188.165.1.1-188.255.1.1]
-Targeted Port Range [20-80]
-Threads [3]
-Delay 10 usec
-Use the [Service] discoverage Plugin

# ./bin/npingu -t 5 -p 80 -s 74.125.0.0-74.225.1.1 #scan google
-Targeted Hosts [74.125.0.0-74.225.1.1]
-Targeted Port [80]
-Threads [5]
-synOnly scan (without plugins)

You can run ninja pingu with the -h flag to get the help.



Source
github.com

~ mercredi 25 juin 2014 0 commentaires

OWASP Xenotix XSS Exploit Framework


http://www.ehacking.net/2013/12/owasp-xenotix-xss-exploit-framework.html
As a web administrator you are responsible to manage the website of your organization, you are working at an organization which sell things through Internet (Ecommerce). One day you came to office and found that the website (brand) has been hacked and confidential information was leaked on the internet (including credit card information of your customers). It is a serious damage and you might be fired by the management because it is your responsibility to manage the website and run the operation effectively and efficiently.

There are so many ways by using the hackers can harm the organization at this level (mentioned above) but cross site script (XSS) is one of the most dangerous and common vulnerability that can be found on every website. Penetration testing is required to manage the security of a website and it could be done by using automatic tools like Xenotix XSS Exploitation Framework.

What is Xenotix XSS Framework

OWASP Xenotix XSS Exploit Framework is an advanced Cross Site Scripting (XSS) vulnerability detection and exploitation framework. It provides Zero False Positive scan results with its unique Triple Browser Engine (Trident, WebKit, and Gecko) embedded scanner.
SCANNER MODULES
  • Manual Mode Scanner
  • Auto Mode Scanner
  • DOM Scanner
  • Multiple Parameter Scanner
  • POST Request Scanner
  • Header Scanner
  • Fuzzer
  • Hidden Parameter Detector
INFORMATION GATHERING MODULES
  • WAF Fingerprinting
  • Victim Fingerprinting
  • Browser Fingerprinting
  • Browser Features Detector
  • Ping Scan
  • Port Scan
  • Internal Network Scan

Download XSS Framework

The latest version (while writing) is 4.5, you can get it from the official website or even from DropBox.

Xenotix XSS Framework Tutorial






Vulnerability assessment is the right process that help you to get rid of these security bugs so that you will not be fired from the job.




Note: If you want to learn more about Linux and Windows based Penetration testing, you might want to subscribe our RSS feed and Email Subscription  or become our Facebook fan! You will get all the latest updates at both the places.

~ jeudi 26 décembre 2013 0 commentaires

OWASP TOP 10 Security RISKS For 2013






The OWASP or the Open Web Application Security Project's "top 10" has been designed to raise awareness about crucial security threats faced by organisations. The data is based on 8 companies specialising in application security out of which 4 are consulting firms and the rest are tool vendors.

The top 10 are selected on the basis of exploitability, detectability and impact estimate from over 500,000 vulnerabilities spanning over hundreds of organisations and thousands of applications. The purpose of which is to educate developers, designers, architects, managers and organisations regarding web application security weaknesses.


The significance of the top 10 project is to understand what web applications can be prone to. OWASP provides additional information regarding these vulnerabilities that help the reader to prevent and combat such risks.

Cheers!

About the Author:
This article is written by Dr.Sindhia Javed Junejo. She is one of the core members of RHA team.

~ samedi 16 février 2013 0 commentaires

Experts Contemplate If OWASP Top 10 List Should Be Changed Or Not?

Open Web Application Security Project (OWASP) is an organization that grabbed the attention of millions through its incomparable services. It’s a Non Profit Organization that alerts the users worldwide about the Security weaknesses of the various applications and many security flaws of various Internet Applications like Internet Banking. It also warns about the security aspects of computers too. Providing updates on all the latest information regarding new web apps has been a top focus of this autonomous body. OWASP continuously assesses the security levels of these applications. Many new internet users find it very handy.

The OWASP Team keeps the entity going


The OWASP Team contains various security experts from multiple domains and the various walks of life. The team is filled with volunteers who strive hard on each project they take up. The job of the team is not so simple, especially given their methodologies and techniques used. They view every aspect with an in-depth purview. The name achieved by the team that “it is non commercial and will not support any company” was attained due to its enormous contribution to the field of technology.

Counting down the list of ‘Top 10’

 
The top 10 list of the most dangerous security applications is published by the organization. It contains valuable information that every person accessing the computer must necessarily be aware of. The list gives an insight into the top 10 security attacks and breaches which were conducted over the years, as recorded and viewed by the various technical experts.

Knowing more about the ‘Top 10’


The Top 10 includes certain key and important procedures to break the security system which is currently in implementation by certain application developers and can be seen in their applications. It covers all the notable aspects and issues like improper error management, failure in buffer management, secured authentication break up, worst session management and failure to save the data packets from being copied by the attackers.

It includes many such things which are quite crucial; utmost attention must be paid while handling these critical applications. These also include certain aspects like Internet banking which is so sensitive that the attacker can steal the money of an innocent individual once he/she gets unauthorized access to the details. Sometimes it also includes the privacy matters of individuals which are extremely confidential.

What are the good pointers of ‘Top 10’?


The list of top 10 broadly helps the users to a large extent. It is because all the users can not go through the entire aspects due to time constraints. Sometimes they may come across the unwanted stuff that is of no use to them. But these top ten lists are very crucial and almost every user will find it useful. It guides them to choose the better security application versions among the available applications. The OWASP is of the view that the Top 10 pointers mentioned in the list are more important than many new threats. Hence they may prefer to continue with the same list. The list of top 10 for the year 2012 is yet to be declared, though the experts are not expecting too many changes in it.

In spite of many arguments, one should not ignore the great contribution of the organization to various computer users. We can only anticipate that the new OWASP Top 10 will emerge in future with flying colours and will be a force to reckon with.

Tom Rhoddings is a freelance writer and author of this guest post. He helps provide useful tips in the field of application security.



Note: If you want to learn more about Linux and Windows based Penetration testing, you might want to subscribe our RSS feed and Email Subscription  or become our Facebook fan! You will get all the latest updates at both the places.

~ vendredi 25 janvier 2013 0 commentaires

OWASP Top 10 Vulnerabilities & Exploitation

Once upon a time there was no Internet and there was no concept of the Web. But time has passed and today we have a technology called the Internet.
In earlier versions of the Internet there were only static web pages with limited ability to interact with users. Today every business has its own identity on the Internet and there is advance commerce taking place online. Businesses depend on the Internet because of its high flexibility and speed. The main point I want to discuss is the importance of web applications. The era of static web pages is over and now we have user-friendly web pages that built from multiple types of scripts (Perl, PHP, ASP, etc.).

So the importance of web applications is not a hidden truth and the security of web application is necessary to protect information from strangers (black-hat hackers). Web applications are on the hit list of hackers because they are easy to access, and the risk is high for both system and user. From the systems point of view we need to protect the integrity and reputation of the system. From the user’s perspective we need to care about identity, privacy, money and other things.

Open Web Application Security Project (OWASP) is an open source community for application level security projects and OWASP has defined or created a list of the top vulnerabilities and security risks for web applications. This list is commonly known as the OWASP Top 10. The top ten vulnerabilities for web applications as defined by OWASP are not the only risks because there are hundreds of other issues and vulnerabilities that may occur on a web application.

The OWASP Top 10 are the most critical and common vulnerabilities that can cause a system to compromise the user information.

OWASP Top 10
 
  1. Injection
  2. Cross-Site Scripting (XSS)
  3. Broken Authentication and Session Management
  4. Insecure Direct Object References
  5. Cross-Site Request Forgery (CSRF)
  6. Security Misconfiguration
  7. Insecure Cryptographic Storage
  8. Failure to Restrict URL Access
  9. Insufficient Transport Layer Protection
  10. Unvalidated Redirects and Forwards

In this article we will discuss the security risks and their effect on a web application. This is a good way to create security awareness among web application developers, web masters and users. In this article we will also cover the best open source tools that can be helpful while doing penetration testing on a web application; it is a good practice to conduct a penetration testing on web applications to protect both the system and the users.

Injection

Dynamic web applications are based on bi-directional communication where users are allowed to send data to web application. So in this case a user (internally or externally) might act as a threat agent and they can send simple syntax, query, command and arguments to a web application. Injection flaws are very common and dangerous. They can be discovered by evaluating code, via automatic scanners and the use of fuzzers.

Injection, or code injection, is too general a term. I categorize the different types like this:
  • Command injection
  • SQL injection
  • Blind SQL injection
  • LDAP injection
  • and others (as I said above, there might be hundreds of vulnerabilities that may occur but we will discuss the most dangerous)
SQL (Structured Query Language) injection is treated as a the most dangerous and common web application vulnerability because SQL is a language that is used to manage the data (information) on a database. Due to SQL injection vulnerability an attacker can control the database (that means all the information, including administrator and users’ confidential information) and can execute commands on the server (that means they have full access).

Open Source Tools to Find Injection Vulnerability in Web Applications
As I said earlier, I will discuss only open source tools (or tools that are available free of cost) while there are some commercial tools that are also available and can be helpful. It is not a hard and fast rule to use the tools that are mentioned here, you can use whatever you want to use.
  • w3af (Web Application Attack and Audit Framework)
  • OWASP ZAP (I prefer and use)
  • HackBar and SQL Inject Me (Firefox add-ons)
 

To exploit the SQL injection vulnerability an attacker can use automatic tools or manual techniques. The most common tools are:
  • SQLmap
  • SQLninja

Cross-Site Scripting (XSS)

XSS or Cross-Site Scripting is another dangerous and common web application vulnerability and can be categorized under the heading of an injection attack because in XSS a malicious script or syntax is injected into a web server. In simple words, cross-site scripting is an attack in which an attacker injects malicious code into a web application and the server sends this page to the browser (other users) without any validation of content. The common method or way to execute the syntax is via the guest book, contact form, search bar and other forms that allows user to enter some information.
There are mainly three types of cross-site scripting:
  • Stored
  • Reflected
  • DOM based XSS
In stored XSS the malicious code is permanently stored on a web server (database) via comment and forum message. In reflected XSS the malicious code or script reflects back from the web server in an error window, search result and many other ways. DOM XSS or type-0 XSS is an attack in which the malicious script or payload modifies the DOM environment on the victim (other user) side by using a client side attack vector.

The risk factor of XSS is high because user information can be stolen via XSS vulnerability. Session hijacking, cookies stealing, phishing (redirecting users to another malicious website), website defacement and an attacker can control the victim’s web browser and then their operating system.

Open Source Tools to Find Cross-Site Scripting Vulnerability in Web Applications
  • OWASP ZAP
  • DOMinator (A Firefox based plugin for DOM XSS)
  • XSSer (Cross Site “Scripter” is an automatic framework used to detect, exploit and report XSS vulnerabilities in web-based applications.)
There are different ways and techniques to exploit the XSS vulnerability, like phishing and others discussed above. Besides manual technique, these common tools can be helpful:
  • XSS Shell
  • BeEF XSS Framework  
This is the series article on OWASP Top 10 and the next article of this series will be publish soon !






















    Note: If you want to learn more about Linux and Windows based Penetration testing, you might want to subscribe our RSS feed and Email Subscription  or become our Facebook fan! You will get all the latest updates at both the places.

    ~ mercredi 11 juillet 2012 0 commentaires