Skip to main content

Posts

Showing posts from 2013

Wireless Hacking - part1

GITHUB CORNER - WIRELESS HACKING EDITION Infernal-  Wireless  This is  automated  wireless  hacking tool ##Infernal-Wireless v2.6 Release 2.6.11 ##Features added and improved: • Menu to retrieve logs are added ##Infernal-Wireless v2.6 Release 2.6.10 ##Features added and improved: • Added BeeF XSS framework Integration • Added HTTP Traffic View within tool • Improved Infenral Wireless Attack • Visual View of some of the panel improved • Improved Basic Authentication during Social engineering assessment over wireless network Infernal-Wireless v2.6 This tool is created to aid the penetration testers in assessing wireless security. Author is not responsible for misuse. Please read instructions thoroughly.Usage: python InfernalWireless.py (from the same folder where your code exists) For any comments and suggestions please email on 1337[@]gmail[dot]com ##BUG Fixes: 1. Non ASCII SSID Name used to crash the software. It is fixed now 2. Warnings on the backgrou

Web Application Hacking - Part4

NoSQL Injection Continuing from module 3, and the analysis of other Injection methods, let’s examine NoSQL and how to perform injection attacks to it. The term NoSQL is used to refer to various data stores that break from standard relational database architectures. NoSQL data stores represent data using key/value mappings and do not rely on a fixed schema such as a conventional database table. Keys and values can be arbitrarily defined, and the format of the value generally is not relevant to the data store. A further feature of key/value storage is that a value may be a data structure itself, allowing hierarchical storage, unlike the flat data structure inside a database schema. NoSQL advocates claim this has several advantages, mainly in handling very large data sets, where the data store’s hierarchical structure can be optimized exactly as required to reduce the overhead in retrieving data sets. In these instances, a conventional database may require complex cross-referencing of

Web Application Hacking - Part3

SQL Injection Encoding and Evasion Techniques So far, we have seen many advanced attacks for SQL Injection that may be lethal for our database. These attacks will many times be possible but they may not seem to be able to be executed. This is a result of some safety methods (which we will examine in module 4) that filter our input. To bypass these restrictions, let’s examine some of the most famous ways. URL Encoding URLs are permitted to contain only the printable characters in the US-ASCII character set — that is, those whose ASCII code is in the range 0x20 to 0x7e, inclusive. Furthermore, several characters within this range are restricted because they have special meaning within the URL scheme itself or within the HTTP protocol. The URL-encoding scheme is used to encode any problematic characters within the extended ASCII character set so that they can be safely transported over HTTP. The URL-encoded form of any character is the % prefix followed by the character’s two-di