Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Is there a way to crack the password on an Excel VBA Project?

I've been asked to update some Excel 2003 macros, but the VBA projects are password protected, and it seems there's a lack of documentation... no-one knows the passwords.

Is there a way of removing or cracking the password on a VBA project?

like image 595
Jonathan Sayce Avatar asked Jun 22 '09 10:06

Jonathan Sayce


People also ask

Is it possible to crack Excel password?

A password protected excel file can sometimes be recovered using specific tools such as HashCat or John the Ripper. These are quite technical password "cracking" programs. Older versions of office (prior to office 2010) had quite weak password hashing algorithms but the newer versions are much harder to recover.


2 Answers

You can try this direct VBA approach which doesn't require HEX editing. It will work for any files (*.xls, *.xlsm, *.xlam ...).

Tested and works on:

Excel 2007
Excel 2010
Excel 2013 - 32 bit version
Excel 2016 - 32 bit version

Looking for 64 bit version? See this answer

How it works

I will try my best to explain how it works - please excuse my English.

  1. The VBE will call a system function to create the password dialog box.
  2. If user enters the right password and click OK, this function returns 1. If user enters the wrong password or click Cancel, this function returns 0.
  3. After the dialog box is closed, the VBE checks the returned value of the system function
  4. if this value is 1, the VBE will "think" that the password is right, hence the locked VBA project will be opened.
  5. The code below swaps the memory of the original function used to display the password dialog with a user defined function that will always return 1 when being called.

Using the code

Please backup your files first!

  1. Open the file(s) that contain your locked VBA Projects
  2. Create a new xlsm file and store this code in Module1

    code credited to Siwtom (nick name), a Vietnamese developer

    Option Explicit  Private Const PAGE_EXECUTE_READWRITE = &H40  Private Declare Sub MoveMemory Lib "kernel32" Alias "RtlMoveMemory" _         (Destination As Long, Source As Long, ByVal Length As Long)  Private Declare Function VirtualProtect Lib "kernel32" (lpAddress As Long, _         ByVal dwSize As Long, ByVal flNewProtect As Long, lpflOldProtect As Long) As Long  Private Declare Function GetModuleHandleA Lib "kernel32" (ByVal lpModuleName As String) As Long  Private Declare Function GetProcAddress Lib "kernel32" (ByVal hModule As Long, _         ByVal lpProcName As String) As Long  Private Declare Function DialogBoxParam Lib "user32" Alias "DialogBoxParamA" (ByVal hInstance As Long, _         ByVal pTemplateName As Long, ByVal hWndParent As Long, _         ByVal lpDialogFunc As Long, ByVal dwInitParam As Long) As Integer  Dim HookBytes(0 To 5) As Byte Dim OriginBytes(0 To 5) As Byte Dim pFunc As Long Dim Flag As Boolean  Private Function GetPtr(ByVal Value As Long) As Long     GetPtr = Value End Function  Public Sub RecoverBytes()     If Flag Then MoveMemory ByVal pFunc, ByVal VarPtr(OriginBytes(0)), 6 End Sub  Public Function Hook() As Boolean     Dim TmpBytes(0 To 5) As Byte     Dim p As Long     Dim OriginProtect As Long      Hook = False      pFunc = GetProcAddress(GetModuleHandleA("user32.dll"), "DialogBoxParamA")       If VirtualProtect(ByVal pFunc, 6, PAGE_EXECUTE_READWRITE, OriginProtect) <> 0 Then          MoveMemory ByVal VarPtr(TmpBytes(0)), ByVal pFunc, 6         If TmpBytes(0) <> &H68 Then              MoveMemory ByVal VarPtr(OriginBytes(0)), ByVal pFunc, 6              p = GetPtr(AddressOf MyDialogBoxParam)              HookBytes(0) = &H68             MoveMemory ByVal VarPtr(HookBytes(1)), ByVal VarPtr(p), 4             HookBytes(5) = &HC3              MoveMemory ByVal pFunc, ByVal VarPtr(HookBytes(0)), 6             Flag = True             Hook = True         End If     End If End Function  Private Function MyDialogBoxParam(ByVal hInstance As Long, _         ByVal pTemplateName As Long, ByVal hWndParent As Long, _         ByVal lpDialogFunc As Long, ByVal dwInitParam As Long) As Integer     If pTemplateName = 4070 Then         MyDialogBoxParam = 1     Else         RecoverBytes         MyDialogBoxParam = DialogBoxParam(hInstance, pTemplateName, _                            hWndParent, lpDialogFunc, dwInitParam)         Hook     End If End Function 
  3. Paste this code under the above code in Module1 and run it

    Sub unprotected()     If Hook Then         MsgBox "VBA Project is unprotected!", vbInformation, "*****"     End If End Sub 
  4. Come back to your VBA Projects and enjoy.

like image 101
Đức Thanh Nguyễn Avatar answered Oct 04 '22 21:10

Đức Thanh Nguyễn


Yes there is, as long as you are using a .xls format spreadsheet (the default for Excel up to 2003). For Excel 2007 onwards, the default is .xlsx, which is a fairly secure format, and this method will not work.

As Treb says, it's a simple comparison. One method is to simply swap out the password entry in the file using a hex editor (see Hex editors for Windows). Step by step example:

  1. Create a new simple excel file.
  2. In the VBA part, set a simple password (say - 1234).
  3. Save the file and exit. Then check the file size - see Stewbob's gotcha
  4. Open the file you just created with a hex editor.
  5. Copy the lines starting with the following keys:

    CMG=.... DPB=... GC=... 
  6. FIRST BACKUP the excel file you don't know the VBA password for, then open it with your hex editor, and paste the above copied lines from the dummy file.

  7. Save the excel file and exit.
  8. Now, open the excel file you need to see the VBA code in. The password for the VBA code will simply be 1234 (as in the example I'm showing here).

If you need to work with Excel 2007 or 2010, there are some other answers below which might help, particularly these: 1, 2, 3.

EDIT Feb 2015: for another method that looks very promising, look at this new answer by Đức Thanh Nguyễn.

like image 41
Colin Pickard Avatar answered Oct 04 '22 21:10

Colin Pickard