Wednesday, March 16, 2011

Ophcrack 3.3.1 & LiveCD – Free Rainbow Table Password Cracking Tool

Ophcrack 3.3.1 & LiveCD – Free Rainbow Table Password Cracking Tool: "Ophcrack is a free Windows password cracker based on rainbow tables. It is a very efficient implementation of rainbow tables done by the inventors of the method. It comes with a Graphical User Interface and runs on multiple platforms. It works based on a time-memory trade-off using rainbow tables.

You can download Ophcrack 3.3.1 here:

Windows – ophcrack-win32-installer-3.3.1.exe
Source – ophcrack-3.3.1.tar.bz2

Or download the LiveCD here:

To crack XP hashes – ophcrack-xp-livecd-2.3.1.iso
To crack Vista hashes – ophcrack-vista-livecd-2.3.1.iso


Features

  • Runs on Windows, Linux/Unix, Mac OS X
  • Cracks LM and NTLM hashes.
  • Free tables available for Windows XP and Vista.
  • Brute-force module for simple passwords.
  • Audit mode and CSV export.
  • Real-time graphs to analyze the passwords.
  • LiveCD available to simplify the cracking.
  • Loads hashes from encrypted SAM recovered from a Windows partition, Vista included.
  • Free and open source software (GPL).

WASC WHID Semi-Annual Report for 2010: July - December

WASC WHID Semi-Annual Report for 2010: July - December: "

SpiderLabs just released our WASC Web Hacking Incident Database (WHID) Semiannual Report for 2010 (July - December). You can download the full report here (registration required). In this report, we analyze the WHID events from the 2nd half of the year and provide information such as top:



  • Outcomes

  • Attacks

  • Application Weaknesses

  • Attacked Vertial Markets

  • Vertical Market Breakdown


Report Summary Findings


An analysis of 75 Web hacking incidents from the second half of 2010 conducted by Trustwave’s SpiderLabs team shows the following trends and findings:



  • A steep rise in attacks aimed at causing downtime – currently the new no. 1 outcome (up 21% from previous reporting period). This is mainly a result of ideological hacking efforts utilizing distributed denial of service (DDoS) attacks as part of the Anonymous Group versus Anti-Piracy and WikiLeaks events.

  • Corresponding to downtime outcomes, denial of service attacks made the largest jump for Attack Methods to no. 1 (up 22% from the previous reporting period).

  • Organizations have not properly implemented nor tested anti-automation defenses for their Web application architecture to ensure application availability during denial of service (DoS) attacks.


Vertical Market Breakdown


The most valuable way to use WHID data is to apply a vertical market view. This will give you a much closer view of what issues are effecting your market. To this, you can utilize the Real-time Statistics interface on the WHID Project Site and choose your vertical market from the drop-down list. Here is quick breakdown of the top vertical markets from 2010:


Government



  • Outcome – Defacement

  • Attack Method – SQL Injection

  • Application Weakness – Improper Input Handling


Finance



  • Outcome – Monetary Loss

  • Attack Method – Stolen Credentials

  • Application Weakness – Insufficient Authentication


Retail



  • Outcome – Credit Card Leakage

  • Attack Method – SQL Injection

  • Application Weakness – Improper Input Handling




WHID Top 10 Risks for 2010


As part of the WHID analysis, here is a current Top 10 listing for 2010 of the application weaknesses that are actively being exploited (with example attack method mapping in parentheses). Hopefully this data can be used by organizations to re-prioritize their remediation efforts.





















































WHID Top 10 for 2010



1



Insufficient Anti-Automation (Brute Force and DoS)



2



Improper Output Handling (XSS and Planting of Malware)



3



Improper Input Handling (SQL Injection)



4



Insufficient Authentication (Stolen Credentials/Banking Trojans)



5



Application Misconfiguration (Detailed error messages)



6



Insufficient Process Validation (CSRF and DNS Hijacking)



7



Insufficient Authorization (Predictable Resource Location/Forceful Browsing)



8



Abuse of Functionality (CSRF/Click-Fraud)



9



Insufficient Password Recovery (Brute Force)



10



Insecure Indexing (Search Engines)



Attack Likelihood Metrics


Another use for WHID data is to help provide event likelihood data for various industry web application security efforts such as:



Both of the reports have historically been heavily weighted towards vulnerability prevalence. Hopefully, WHID data can assist both of these efforts when creating future versions by providing data on event likelihood which in turn would help to re-prioritize the rankings of issues.




"

Links and Notes

Links and Notes: "Forensic Meet-up
There are plans afoot for a forensics meet-up in the Northern VA area (Chantilly - Centreville - Herndon - Reston) on 31 Mar 2011. The meet-up will likely start around 6:30pm - 7pm, and the location is TBD for the moment...keep an eye here, or on the Win4n6 group. This first meet-up will be free-form, and I'll work up something of an informal agenda.

As more folks become aware of this meet-up, I guess my initial concern would be where to meet. I'd like this to be informal, and everyone to relax and have a beer. If the interest is for something a bit more formal, then we may move to a different agenda later. Eventually, my hope is that this becomes something useful to folks, as we can discuss and implement innovation in the DF and IR fields...

F-Response Patent
On Fri, 11 Mar 2011, Matt announced that F-Response had received a patent for remote forensic innovation! Congrats, Matt...this is very well deserved!

Of specific note is that F-Response provides, '...forensic grade write-protection...' for remote forensics and raw access to systems.

This is fantastic news for Matt, and for the community as a whole! Matt's contributions to the field have been phenomenal, to say the least.

RegRipper Plugins
I recently wrote up some new plugins (and updated the samparse.pl plugin)...

notify.pl - Parses the Notify subkeys within the Software hive for registered Winlogon Notification DLLs, based on Mark's Case of the SysInternals-Blocking Malware post

init_dlls.pl - Checks for keys similar to the one mentioned in Mark's Case of the Malicious AutoStart post

renocide.pl - Checks for an artifact key mentioned on the MMPC site for the Win32/Renocide malware

These plugins are meant to demonstrate a couple of things...first, that Registry analysis can be used in conjunction with other analysis methods to detect malware within acquired images, where AV scanners might fail. I've run AV scans before where two commercial and three free AV scanners didn't find anything, but the fourth free scanner found something. I've also seen where AV used by customers has failed due not to having the incorrect DAT file, but to having the incorrect scanning engine. We're all susceptible to this, and if you use AV as part of your malware detection process for when you examine acquired images, then this is something that you'll need to be aware of, as well.

Second, all three of these plugins took me less than 30 minutes...total...to write and test. In fact, the only real slow-down was deciding how to make the output a bit more useful...for the notify.pl plugin, I copied code from the userassist.pl plugin to list all of registered DLLs sorted based on their key LastWrite times. This means that if I want to deploy any of these plugins as part of my timeline creation toolkit, it's simply a matter of minutes for me to modify them. So in less than 30 minutes, I was able to add three new plugins to the library, and saved everyone who uses those plugins the time for researching and writing those plugins themselves. This serves not only as a force multiplier, but also as a library for institutional knowledge within the community as a whole.

You can get copies of these plugins from Brett's RegRipper.net site.

As a side note, running RegRipper is just part of the malware detection process that I use regularly, and what I'm writing about and detailing for my next book. Part of the supporting materials for this book will include a checklist, as well.
"

EnScript to parse classic (.evt) event log entries in unallocated

EnScript to parse classic (.evt) event log entries in unallocated: "
This EnScript was inspired by a blog reader who emailed me to ask for a solution to parse some windows event log entries that were found in unallocated.


There are a couple ways I could think of to solve this issue. The easiest was to just build a parser to read a single event log record that was found in unallocated and display the data in the single record. The problem with that solution is it does not scale well and it will become very tedious when there are numerous records found in unallocated and requires a person to parse each one individually.


The final solution was an EnScript to perform a search for the magic value of "LfLe" which appears in every valid event log record. Once a hit is found, then the record is parsed and exported out into a separate .EVT file. Every hit is exported out into the same .evt file and in the end, you will have a single "eventlog.evt" that contains all the valid windows event log entries that were found in unallocated. You can then use your favorite 3rd party event log viewer (Event log explorer, etc..) or the native Windows event viewer (eventvwr.exe) to read all the records that were found in unallocated.


Each event log entry maintains a event record number. When searching in unallocated, it is possible that you could find two records with the same record number, therefore this EnScript renumbers all the records found in unallocated, but leaves the remaining data intact and as exactly as found in unallocated. Each record is assigned a new record number and then exported into the new .Evt file. A new header and footer is built based on the exported data so it can then be read with all the common event log viewing tools.


The exported records viewed in the EVENTVWR app in Windows 7:






The exported records viewed in the Event Log Explorer app in Windows 7:





Prerequisites:
None - This EnScript performs a search automatically. There is no need to search, select (blue check) or preprocess anything. The EnScript will search every unallocated object found, so if you have multiple drives loaded into the case, each one will be searched automatically. The EnScript automatically bookmarks all the 'LfLe' search hits (valid and invalid). Some basic error checking is done to validate the record to attempt to ensure it is a complete and valid record before it is exported into the new .EVT file. The new 'eventlog.evt' file is created in the default export folder for the active case.


Limitations:
This *only* searches and rebuilds classic Windows NT/2000/XP event (.evt) records. It does not yet support the newer .EVTX (xml) records that are used in Vista, 2008 & 7.


Download here
"

"Understanding EXT4 (Part 2): Timestamps"

"Understanding EXT4 (Part 2): Timestamps": "Hal Pomeranz, Deer Run AssociatesWell I certainly didn't plan on three months elapsing between my last post on EXT4 and this follow-up, but time marches on. That was supposed to be a clever segue into the topic for this installment-- the new timestamp format in the EXT4 inode. OK, I know what you all are thinking now: "Shut up Hal and get to the geeky stuff." Your wish is my command!Setting the StageLet's set up another test file in an EXT4 file ssytem:# echo Time for knowledge >testfile# touch -a -t 211101231917.42 testfile# touch -m -t 204005160308.19 testfileI'm using the touch command as root to ..."

Friday, January 15, 2010

Selective Domain/Forest Trusts – episode I

 

Max, my buddy recently shared a concern he had in his organization (say Piglet Inc.,). They just acquired another company (say Ducklings Inc.,) and now they have trust relationship between the two ADs. He is paranoid about this level of trust due to the fact that the other domain/forest is not directly managed by his IT department. A very useful feature in such a scenario is “Selective Trusts”. This feature is inherent in Windows 2003 and can be used as long the forest functional level is set to windows 2003, in the trusting domain. Ofcourse, if the trust is a two-way transitive trust, then both the forest should be at the “windows 2003” functional level.

A simple netdom command will put his concerns to rest and get him to sleep better.

on the trusting domain, enter the below netdom command:

Netdom trust <trustingDomainName> /domain:<trustedDomainName> /SelectiveAuth:Yes
/usero:<domainadministratoraccount> /passwordo:<domainadministratoraccountpassword>

eg:-

Netdom trust piget.com /domain:duckling.com /selectiveAuth:Yes
/usero:pigletadmin /passwordo:oinkoink

To disable Selective Trust, just issue the same command with /SelectiveAuth:No

By doing this, you can pick and choose which users or groups get access to what resources or computers in your domain.

Let’s say for example, Scrooge from HR team in Duckling Inc., needs access a share on Piglet’s HR File server named “Porkie”, under normal circumstances, Scrooge would try to access it using the below URL: \\Porkie\sharename, and as long as he had access to the share, he could get in. And if “Authenticated Users” had access to the share, then he wouldn’t even need any more access privileges, he would just get in.

But, with Selective Auth on, this would not work. There is a special Object access right “Allowed to Authenticate” that needs to be granted to Scrooge on the computer object “Porkie”, before he can get access to the resources.

How does this actually work in the background ???? Well that’s for episode II

Friday, September 18, 2009

Empathy the new IM for Gnome

Historically, Pidgin has been the choice of IMs provided with Gnome or Linux. Pidgin has been the choice of multi-protocol clients for a huge crowd including windows enthusiants too. It enjoys a loyal following of developers and supporters from across the globe, who have volunteered a lot of plug-ins to Pidgin. This has made Pidgin quite a heavy app. I have been waiting to test Empathy from the time i heard it was in the works by the Gnome Development team.

A little bit about Empathy. Empathy is a messaging client that supports text messaging, Voice and most importantly Video calls. It also supports File transfer over XMPP or local networks, which I am not too keen on, but the support for Video chat in a multi-protocol IM is awesome. It supports Voice and Video using the open protocols, SIP and XMPP (think jabber and jingle). Empathy also supports location information.

Installing Empathy could be as easy as running

# yum install empathy

Loaded plugins: refresh-packagekit
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package empathy.x86_64 0:2.26.2-1.fc11 set to be updated
--> Processing Dependency: telepathy-salut for package: empathy-2.26.2-1.fc11.x86_64
--> Processing Dependency: telepathy-haze for package: empathy-2.26.2-1.fc11.x86_64
--> Processing Dependency: telepathy-gabble for package: empathy-2.26.2-1.fc11.x86_64
--> Processing Dependency: telepathy-filesystem for package: empathy-2.26.2-1.fc11.x86_64
--> Running transaction check
---> Package telepathy-filesystem.noarch 0:0.0.1-3.fc11 set to be updated
---> Package telepathy-gabble.x86_64 0:0.7.26-2.fc11 set to be updated
--> Processing Dependency: libloudmouth-1.so.0()(64bit) for package: telepathy-gabble-0.7.26-2.fc11.x86_64
---> Package telepathy-haze.x86_64 0:0.3.1-1.fc11 set to be updated
---> Package telepathy-salut.x86_64 0:0.3.9-1.fc11 set to be updated
--> Processing Dependency: libavahi-gobject.so.0()(64bit) for package: telepathy-salut-0.3.9-1.fc11.x86_64
--> Running transaction check
---> Package avahi-gobject.x86_64 0:0.6.25-3.fc11 set to be updated
---> Package loudmouth.x86_64 0:1.4.3-5.fc11 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
Package                   Arch        Version               Repository    Size
================================================================================
Installing:
empathy                   x86_64      2.26.2-1.fc11         updates      1.4 M
Installing for dependencies:
avahi-gobject             x86_64      0.6.25-3.fc11         updates       30 k
loudmouth                 x86_64      1.4.3-5.fc11          updates       79 k
telepathy-filesystem      noarch      0.0.1-3.fc11          fedora       3.5 k
telepathy-gabble          x86_64      0.7.26-2.fc11         updates      330 k
telepathy-haze            x86_64      0.3.1-1.fc11          updates       57 k
telepathy-salut           x86_64      0.3.9-1.fc11          fedora       248 k

Transaction Summary
================================================================================
Install      7 Package(s)        
Update       0 Package(s)        
Remove       0 Package(s)        

Total download size: 2.1 M
Is this ok [y/N]: y
Downloading Packages:
(1/7): avahi-gobject-0.6.25-3.fc11.x86_64.rpm            |  30 kB     00:01    
(2/7): empathy-2.26.2-1.fc11.x86_64.rpm                  | 1.4 MB     00:20    
(3/7): loudmouth-1.4.3-5.fc11.x86_64.rpm                 |  79 kB     00:02    
(4/7): telepathy-filesystem-0.0.1-3.fc11.noarch.rpm      | 3.5 kB     00:00    
(5/7): telepathy-gabble-0.7.26-2.fc11.x86_64.rpm         | 330 kB     00:07    
(6/7): telepathy-haze-0.3.1-1.fc11.x86_64.rpm            |  57 kB     00:03    
(7/7): telepathy-salut-0.3.9-1.fc11.x86_64.rpm           | 248 kB     00:01    
--------------------------------------------------------------------------------
Total                                            53 kB/s | 2.1 MB     00:40    
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing     : telepathy-filesystem-0.0.1-3.fc11.noarch                 1/7
  Installing     : telepathy-haze-0.3.1-1.fc11.x86_64                       2/7
  Installing     : avahi-gobject-0.6.25-3.fc11.x86_64                       3/7
  Installing     : telepathy-salut-0.3.9-1.fc11.x86_64                      4/7
  Installing     : loudmouth-1.4.3-5.fc11.x86_64                            5/7
  Installing     : telepathy-gabble-0.7.26-2.fc11.x86_64                    6/7
  Installing     : empathy-2.26.2-1.fc11.x86_64                             7/7

Installed:
  empathy.x86_64 0:2.26.2-1.fc11                                               

Dependency Installed:
  avahi-gobject.x86_64 0:0.6.25-3.fc11                                         
  loudmouth.x86_64 0:1.4.3-5.fc11                                              
  telepathy-filesystem.noarch 0:0.0.1-3.fc11                                   
  telepathy-gabble.x86_64 0:0.7.26-2.fc11                                      
  telepathy-haze.x86_64 0:0.3.1-1.fc11                                         
  telepathy-salut.x86_64 0:0.3.9-1.fc11                                        

Complete!

or

# apt-get install empathy

based on your distribution. you can also build it from the sources. I use Fedora 11 and i had to have farsight2 and gstramer-plugins installed to get video and voice calls working. Once empathy starts you can add your yahoo and gtalk accounts…even MSN accounts without any problems. Just remember to change the default ports to 80 instead.

Video and Voice using gtalk work flawlessly.

I like the smoother interface of Empathy and the clean look. Thanks to the team, they did a wonderful job.