Home > Articles > Home & Office Computing > Microsoft Windows Desktop

  • Print
  • + Share This
Like this article? We recommend

Building a Cracker

The following discussion applies to almost any program that encrypts data. The point here is to illustrate how easy it is to turn a valid program’s encryption/decryption routine into an attack vector that can crack the very files it’s meant to protect. All the more reason why it’s essential for you to use a strong password; otherwise, your data may be minutes away from being exposed.

Up to this point, the focus of this article has been demonstrating how an attacker can use a debugger to bypass flawed encryption schemes. We’ve seen that it’s fairly easy to locate the password verification routine, as it comes into the program from the user interface, or through the error message that often appears when a program rejects the wrong password. However, yet another attack vector can be used to gain access to protected data: cracking the password itself.

Any security professional will tell you that implementing an encryption algorithm is incredibly tricky. Even if the algorithm is strong enough to keep the data sufficiently protected, it must be implemented properly, or the protection efforts are essentially worthless. Ironically, due to the nature of most encryption products, a dedicated person can turn the developer’s code against the user.

Airscanner’s tradition is to return to programs where we’ve discovered bugs, in order to see whether the vendor has fixed the problems. We understand that to error is human, and if a company fixes its software, we can update our security alerts. Following that logic, we revisited the previously mentioned bugs in CodeWallet and tried to duplicate the previous finding—but failed. In other words, to our best knowledge, CodeWallet 6.62 is not longer a security risk and we can recommend this software—as long as the user selects a strong password!

During our research into this program, we discovered that the entered password is converted from its x number of characters into a 128-bit string that’s stored in the header of the file. This value is an encrypted hash of the original password, which means that anyone who wants to crack a CodeWallet file has to figure out how this hash is created and use that information as leverage against the encryption.

There are two ways in which a person can defeat a hash. The first and most commonly used method is to "brute force" your way through the hash. One program that performs this function rather well is known as Cain, from the Cain and Abel suite. As Figure 11 shows, Cain can crack any number of algorithms, and quite quickly—assuming that the user selected a weak password.

Figure 11

Figure 11 Cain’s password cracker.

The second method of defeating a hash is to bump up the hash against a pre-calculated "rainbow" table. This table is created offsite (typically by powerful supercomputers) by taking a very long list of possible password values and passing those values through the hashing algorithm. The end result is a list of passwords with their respective hashes. In order to "crack" a specific password, a malicious hacker just has to search the rainbow table for a hash match, which then can be linked directly to the original password.

With either technique, you have to know how the hash is generated from the given password. As illustrated with Cain, numerous algorithms out there can be used for this purpose. However, it appears that CodeWallet is using its own hashing/encryption algorithm. As a result, it’s impossible to take the password hash stored in the data file and run it through existing hash-cracking programs.

Instead, you could tweak the CodeWallet binary file to crack the password.

It appears that CodeWallet first turns the entered password into a hash via a proprietary algorithm, and then encrypts that value via the RC4 algorithm, using the entered password as its seed. This is only an educated guess, but if we’re correct, this isn’t a bad way to protect the password. There are better ways, but they involve public/private keys or a stronger form of encryption.

Following is a summary of how CodeWallet works:

  1. CodeWallet is executed, the wallet is selected, and the password window opens.
  2. The password is entered and the user clicks OK.
  3. GetWindowText captures the password and places it on the memory stack.
  4. The password is hashed and then encrypted to create a 128-bit key.
  5. The memcmp function compares the key from the file with the newly encrypted password.
  6. If the two match, the file is decrypted. If not, the user is warned that the wrong password was entered.

What would happen if someone patched the binary file to do the following instead?

  1. CodeWallet is executed, the wallet is selected, and the password window opens.
  2. The password is entered and the user clicks OK.
  3. Redirect to patch.
  4. One (1) is added to a hardcoded starting value, that value is written to memory for storage, and that value is placed on the stack.
  5. Redirect to the main program.
  6. The calculated password is hashed and then encrypted to create a 128-bit key.
  7. The memcmp function compares the key from the file with the newly encrypted password.
  8. Redirect to patch.
  9. The results are compared. If they match, the password is shown in a message box. If no match exists, the previous password is extracted from memory, one is added, and the result is placed on the stack.
  10. All variables are reset.
  11. Redirect to entry point for continued calculations.

The end result? CodeWallet should brute-force crack the password by iterating up through all possible values, checking each one until it finds the match. While nice in theory, we decided to test the idea and got to work creating a proof of concept that turned out to be a bit of a challenge.

After dealing with a few unexpected obstacles, such as enabling write access to the binary in the PE header, including a piece of code to reset the stack address, patching the binary to get around a few quirks that arose, and dealing with a NULL (0x00) byte bug, we had a password cracker that would crack any four-character ASCII password you can find on the keyboard. Figure 12 illustrates the results.

Figure 12

Figure 12 CodeWallet password.

Again, this doesn’t mean that CodeWallet is insecure—it just indicates why you should never use a four-character password to protect your sensitive data. Given enough time/motivation, any protection can be cracked. The goal for a software vendor is to balance the user’s needs with the technology to best represent those needs. Unfortunately, this balance sometimes means putting a little bit of the responsibility in the user’s camp, which consequentially can lead to inadequate security.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020