My link

If u have any query mail me on


Sunday, 22 February 2015

How to check your VPN is Secure or Not

A new security flaw can reveal your real IP address to prying eyes, even if you're using a VPN, and it's easy to exploit. Here's how it works, and what you can do about it. A recently discovered security flaw allows remote sites to take advantage of WebRTC (Web Real Time Communication, a feature built in to most browsers.

A few lines of code is all it takes to remove the location protection you get from using a VPN, and figure out where you're actually located and who your internet service provider really is (who can then tie your address back to who you are specifically.) While the vulnerability is primarily browser-based right now, any application that can render web pages (and uses WebRTC) is affected, meaning anyone who wants to can see past your VPN to where you really are and who you really are. Advertisers, data brokers, and governments can use it to peek through your VPN to find out where your connection is really coming from.

How Can I Check If My VPN Is Affected?

Firefox and Chrome have implemented WebRTC that allow requests to STUN servers be made that will return the local and public IP addresses for the user. These request results are available to javascript, so you can now obtain a users local and public IP addresses in javascript. This demo is an example implementation of that.

Additionally, these STUN requests are made outside of the normal XMLHttpRequest procedure, so they are not visible in the developer console or able to be blocked by plugins such as AdBlockPlus or Ghostery. This makes these types of requests available for online tracking if an advertiser sets up a STUN server with a wildcard domain.

To see if your VPN is affected:

1) Visit:

and Note down your actual ISP-provided IP address.

2.) Log in to your VPN, choose an exit server in another country (or use whichever exit server you prefer) and verify you're connected.

3.) Go back to What Is My IP Address and check your IP address again. You should see a new address, one that corresponds with your VPN and the country you selected.

4.) Visit Roseler's WebRTC test page

If both tools show your VPN's IP address, then you're in the clear. However, if What Is My IP Address shows your VPN and the WebRTC test shows your normal IP address, then your browser is leaking your ISP-provided address to the world.

The Easy Way: Disable WebRTC In Your Browser.

Chrome, Firefox, and Opera (and browsers based on them) generally have WebRTC enabled by default. Safari and Internet Explorer don't, and thus aren't affected (unless you've specifically enabled WebRTC.) Either way, if the test above worked in your browser, you're affected. You can always switch to a browser that doesn't have WebRTC enabled, but since most of us like the browsers we use, here's what to do:

Chrome and Opera:
Install RTC Block or ScriptSafe extension from the Chrome Web Store. It's overkill, but it'll disable WebRTC in your browser.

Firefox: You have two options. You can install the Disable WebRTC addon from Mozilla Add-ons

or disable WebRTC directly by opening a tab and going to

PHP Code:
in the address bar. Find and set the

PHP Code:
setting to false.

To be sure WebRTC is disabled go to:
And you should see something like this, if your good.

Otherwise you will see this:
I know a lot of you use VPN software and probably don't know about this so I hope it was helpful. Got to stay antonymous if you are hacking websites.

Source: mobi13_XT

Sunday, 7 September 2014

Web Server Cookie Disclouser Vulnerability Scanner

Hello Guys,
           I have write a Python code for checking Web Application Vulnerability

HTTP Only cookie is only accessed from the server side, no client script can access that cookie, when a webserver get a big cookie like same 10000 of characters for example A is char, it cannot process so it get us back error 400 [bad request], in that error has a vulnerability, its disclose cookies on a webserver.
Most of all dont know about the how to check a HTTPOnly vulnerability and web server Cookie Disclouser Vulnerability, some People runs a Tools like Acunetix and burp scan or netsparker there are most of time you will see a HTTPOnly flag is not set or cookies not protected, they just saw it and patched it through .htaccess file or including scripts in php headers file to protect a web server. But Most of dnt know how to check it, So i made it a script for checking specially for cookie disclouser vulnerability on web server
[+] I Have Made a Python Script for Checking HTTPOnly and Web server Cookie Disclouser Vulnerability.
[+] Test it Manually for checking vulnerability of HttpOnly on Web Applications, this is very common vulnerabilty on nowadays [+] Impact of this Vulnerability is Low as well as Medium depending upon the Attacker :D
[+] Using of this python file on windows is very Simple
[+] Download a python for windows from here:
[+] Run a python File [+] C:\python27>python.exe and file path
Here is some Screenshots:
[+] If Target is Vulnerable

[+] If Target is Not Vulnerable

[+] Proof of Exploiting Vulnerability using Browser, Need an Cookie Manager

Download the Python Code from here:

Direct Link: 

Friday, 18 April 2014

Heartbleed Testing Tools [OpenSSL |CVE-2014-0160]

HeartBleed Response with Vulnerable System:-

 Here's a nice collection of heart bleed tools to help you along with this exploit:-
'ONLINE' OpenSSL Heartbleed Vulnerability Scanner: 
This is for those of you in this thread that are having trouble with the Python scripts below

A Checker:  (site and tool) for CVE-2014-0160:
-- Quick and dirty demonstration of CVE-2014-0160 by Jared Stafford
-- (modified version) Added URL crawler and auto-detection function, reducing the trouble to manually enter the URL. You can also use a proxy server, so you can choose your own search engine in the code, and change their keywords. Feel free to edit/modify to suit your needs.
-- (modified version #2) This version is updated for handling different version of SSL/TLS
-- Pacemaker Attempts to abuse OpenSSL clients that are vulnerable to Heartbleed (CVE-2014-0160). Compatible with Python 2 and 3.

SSL Server Test:

Metasploit Module:

Nmap NSE script: Detects whether a server is vulnerable to the OpenSSL Heartbleed:

Nmap NSE script: Quick'n'Dirty OpenVAS nasl wrapper for ssl_heartbleed based on ssl_cert_expiry.nas

Heartbleeder: Tests your servers for OpenSSL:

Heartbleed Attack POC and Mass Scanner:

Heartbleed Honeypot Script:

Bleed Out Heartbleed Command Line Tool v.
Bleed Out is a command line tool written in C# for targeting instances of OpenSSL made vulnerable by the prolific "Heartbleed" bug. The tool aggressively exploits the OpenSSL vulnerability, dumping both ASCII and binary data to files. It also checks the uniqueness of each chunk before persisting it, to ensure that duplicate chunks are not saved.

Windows CMD example:
C:\Users\frank3nstien\Desktop\BleedOut1.0.0.10-1\Bin>BleedOut -h

Enjoy and Thanks for viewing my Blog

*Greetz to m0bi13_xT and My PC