This blog series will explain the process of hacking SAP password hashes: also know as SAP password hacking. The process of hacking will be explained and appropriate countermeasures will be explained.
Questions that will be answered are:
- Where are SAP password hashes stored?
- Which software do I need to install for hacking the password hash?
- How does the brute force method work?
- How does the simple 10k most used password list attack work?
SAP password hashes
SAP has 3 main password hashes:
- SAP BCODE (oldest one and very weak): not to be used any more
- SAP PASSCODE (less old, stronger than BCODE, but still weak): not to be used any more
- SAP PWDSALTEDHASH (newest, strongest)
New SAP installations only use the newest method by default. Older system still might have stored older versions.
From user password to hash
When a users password is set initially or is changed is it hashed and stored in 2 tables:
- USR02, which contains the current password
- USRPWDHISTORY, which contains the history of the passwords
Older systems or wrongly configured systems store all the 3 password types mentioned above.
To start the password attack you need to get the user ID’s and hashes from the USR02 table.
Methods for getting this data (and many more):
- SE11/SE16N table display
- Write simpel ABAP program
- Database access on low level (HANA, Oracle, etc)
- …. more creative methods….
For this weeks example we will use a couple of testusers. The first 5 users are given simple passwords. The 6th user is given a fully random password.
The attack: from hash back to password
When you have the hashes all of the rest is now outside of the SAP system.
First step is to download a password cracking tool. A very good one is Hashcat.
Warning: this software might be considered as real hacking tool comparable to possesing burglary tools. Either only use on private laptop or after agreement of your local company security team.
Hashcat is based on GPU power and not CPU power. This means the speed of cracking depends on the quality and speed of your graphical card(s). Modern graphics card can have up to 4000 cores. Hashcat is written intelligently to use these 4000 cores via parallel processing or mulitple cards.
Download the software from the site and unzip it on your local PC.
Hashcat requires for cracking BCODES the following format per line:
For the example above this results into the following file:
The brute force method
Let’s start by making a file with only TESTUSER6. This is stored in the file TestuserBcodeHashes.txt.
To start the hacking process goto the CMD command prompt and goto the hashcat directory. Then key in this command:
hashcat64 -a 3 -m 7700 -p : --session=all -o "C:\HC\TestuserBcodeHashes_found.txt" --outfile-format=3 --markov-disable --remove --gpu-temp-abort=80 "C:\HC\TestuserBcodeHashes.txt"
Long command, but some part are simpler: -a 3 means brute force, -m 7700 means hashes are SAP BCODE hashes, file output and output, and very important the command to abort if the GPU temperature exceeds 80 degrees celcius.
For full help options: goto the Hashcat website or key in Hashcat64 –help.
Result of this command is following screen:
The brute force attack will use some common pattern, but as you can see per pattern it takes about 16 hours (faster GPU means less time).
Guessing speed is at 57.000 tries per second, which is about 5 billion tries per day. Having a password with 8 random characters (26 letters, 10 digits, 33 specials) would take 69*69*69*69*69*69*69*69 = 513.000 billion options, meaning it would take 100.000 days.
Pretty good you would say. But nobody uses the brute force method.
Attacking with 10.000 most commonly used password list
People tend to user more simpler and more repetitive passwords. See wikipedia for most common and 10.000 most common used passwords.
You can download the file 10.000 most common here: 10k most common
Again we start now Hashcat tool, but now with different command and we will use the file with all the 6 hashes:
-a 6 -m 7700 -p : --session=all -o "C:\HC\TestuserBcodeHashes_found.txt" --outfile-format=3 --markov-disable --remove --gpu-temp-abort=80 "C:\HC\TestuserBcodeHashes.txt" "C:\HC\10k most common.txt"
Attack mode (wordlist) is choosen and we have given the 10k most common text file as wordlist input.
Recovered passwords: 5 out of 6 in about 0 seconds!
You now can logon with these passwords.
This means that we can decrypt the password way much faster than the theoretical example from previous chapter.
How to protect yourself from password hash attacks?
Prevention 1: set password complexity
Set the password complexity rules to at least 1:
If you have only letters, then the guesses for most users will be 26*26*26*26*26*26*26*26 = 208 billion only.. filtering out the hardly used q and x, it could even be 110 billion only.
Prevention 2: disallow the old hashes
Set paramater login/password_compliance_to_current_policy to 1 to forbid the old passwords to be used (in old systems this might require some testing before it is done in productive system, and changes of old passwords that are there for very long time).
Prevention 3: clean up the old hashes
Use program CLEANUP_PASSWORD_HASH_VALUES to clean up the old hashes:
After checking, start the actual cleanup.
Prevention 4: instructions to basis and authorization team to use the password generator for inital passwords
When generating new password: do use the password generator button. This will generate very complex password. Do use it.
Also you should make it known to basis and authorization team not to use simple and repetitive passwords like Welcome-2018 or Passw0rd! Soon you will see a pattern and can already guess new users passwords that they will select. Tell them to use the password generator.
The next blog will explain on the hacking the SAP PASSCODE.