Daniel Berlin on Security Insight on SAP security, development stuff… and all the rest

6Oct 12

SAP password hash algorithms

Hi there,
in this article, I'd like to summarize what I found out about SAP's password storage mechanism (for SU01 users, not the SecStore).

Basics

The passwords of all users are stored in table USR02 as one (or more) cryptographic hash value(s).
Table USH02 and some others contain the password history (see SAP Note 1484692). This history used to be limited to the last 5 entries per user before NW 7.0; meanwhile the number of entries is customizable via the profile parameter login/password_history_size (see SAP Note 862989).

The hash algorithm has changed several times over time – either due to weaknesses or as a result of the increase in computing performance (see "CODVN H" below).

Per definition, the result of a cryptographic hash function is/should be irreversible, i.e. one cannot/shouldn't be able to retrieve the plain text password from the hash value… but that's the point where the fun starts! 😎
SAP Note 1237762 gives a good overview of hash attacks and has some rather helpful tips on how to prevent them!

The password cracking tool John the Ripper (with the "Jumbo" patch) supports two of SAP's common hash algorithms (CODVN B & F/G). Give it a try, if you're serious about the security of your passwords!

Hash algorithms

This table summarizes the details of all currently available password hash algorithms (as per Q4/2012):

USR02-
CODVN
Algo-
rithm
Max. Passw. LengthPw.
Case
CharsetSaltNotesSAP NoteHash in
USR02-...
A?8upperASCII
(limited)
Character 1-6 of the username
(upper-case)
Unsupported characters (probably the same as with CODVN B) in the password and salt are replaced by an apostrophe (»'«).
Superseded by code version B (automatic migration during logon).
721119BCODE
BMD5-based8upperASCII
(limited)
Username
(upper-case)
Unsupported characters (see note) in the password and salt are replaced by »^«735356BCODE
C-Never implemented-
DMD5-based8upperUTF-8Username
(upper-case)
Superseded by code version E
(but almost identical)
-BCODE
EMD5-based8upperUTF-8Username
(upper-case)
Correction of code version D874738BCODE
FSHA1-based40sensitiveUTF-8Username
(upper-case)
-1488159PASSCODE
G= Code versions B & FBCODE &
PASSCODE
Hgeneric hash
(curr. only iSSHA-1)
40sensitiveUTF-8randomHash algorithm and options can be set via parameter login/password_hash_algorithm991968PWDSALTEDHASH
I= Code versions B, F & HBCODE,
PASSCODE &
PWDSALTEDHASH

The MD5- and SHA1-based algorithms consist of two hash iterations with "some Walld0rf magic" in between — for details, have a look at this posting in the john-users mailing list.

Kernel & profile parameters

The following has an impact on the used hash algorithm:

  • the SAP kernel version
  • the profile parameters:
    • login/password_charset
    • login/password_downwards_compatibility — if available

The following tables show the effect of the above on the hash algorithm on some test-systems:

Sources & further reading

Here's where the information in the above "Hash algorithms" table came from – plus additional resources:

  • SAP Note 2467: Password rules and preventing incorrect logons
  • SAP Note 721119: Logon with (delivered) default user fails
  • SAP Note 735356: Special character in passwords; reactivation not possible
  • SAP Note 862989: New password rules as of SAP NetWeaver 2004s
  • SAP Note 874738: New password hash calculation procedure (code version E)
  • SAP Note 991968: Value list for login/password_hash_algorithm
  • SAP Note 1023437: Downwardly incompatible passwords since NW2004s
  • SAP Note 1237762: Protection against password hash attacks
  • SAP Note 1300104: CUA - New password hash procedures - Background information
  • SAP Note 1458262: Recommended settings for password hash algorithms
  • SAP Note 1484692: Protect read access to password hash value tables
  • SAP Note 1488159: SUIM - RSUSR003 - Incorrect results for CODVN = F

Happy reading — this is really helpful stuff! 😛

3Oct 12

Determine transaction type & status from table TSTC (field CINFO)

Hello programmers,
if you ever wanted to determine the transaction type (dialog, parameter tcode …) and status (locked …), you probably came across table TSTC (where tcodes are defined) and found that this information is encoded in the CINFO field — which contains an old-school hexadecimal value.

Meaning

So… wtf do those CINFO values mean? Here we go:

CINFO (hex)BinaryTypeLocked ?Auth. object check ?
0x000000 0000Dialog transactionnono
0x040000 0100Dialog transactionnoyes
0x200010 0000Dialog transactionyesno
0x240010 0100Dialog transactionyesyes
0x010000 0001Area menu (obsolete)no-
0x210010 0001Area menu (obsolete)yes-
0x020000 0010Parameter / variant transactionno-
0x220010 0010Parameter / variant transactionyes-
0x080000 1000Object transactionnono
0x0C0000 1100Object transactionnoyes
0x280010 1000Object transactionyesno
0x2C0010 1100Object transactionyesyes
0x801000 0000Report transactionnono
0x841000 0100Report transactionnoyes
0xA01010 0000Report transactionyesno
0xA41010 0100Report transactionyesyes
0x901001 0000Report transaction with variantnono
0x941001 0100Report transaction with variantnoyes
0xB01011 0000Report transaction with variantyesno
0xB41011 0100Report transaction with variantyesyes
0x05 (invalid)0000 0101Area menu (obsolete)no-
0x06 (invalid)0000 0110Object transaction -or-
Parameter transaction
no
no
yes
n/a
0x44 (invalid)0100 0100Dialog transactionnoyes

(The CINFO values marked with "invalid" exist, but make no sense… probably because they're relicts created by SAP a long time ago. 😯 )

Bitmasks

According to the above, these are the bitmasks for your own program:

Bitmask (hex)BinaryMeaning
0x000000 0000Dialog transaction
0x010000 0001Area menu
0x020000 0010Parameter / variant transaction
0x080000 1000Object transaction
0x801000 0000Report transaction
0x901001 0000Report transaction with variant
0x040000 0100Flag: Authorization object check ?
0x200010 0000Flag: Locked ?

Example

To get started, either have a look at the report "RSAUDITC_BCE" or try this:

REPORT.
 
TABLES: tstc.
 
* -- Bitmasks
DATA: c_auth TYPE x VALUE '04',
      c_lock TYPE x VALUE '20'.
 
* -- Find all locked transactions
SELECT * FROM tstc.
  CHECK tstc-cinfo O c_lock.
  WRITE: / tstc-tcode, 'is locked'.
ENDSELECT.
 
* -- Find customer transactions w/o authorization check
SELECT * FROM tstc WHERE tcode LIKE 'Y%' OR tcode LIKE 'Z%'.
  CHECK NOT tstc-cinfo O c_auth.
  WRITE: / tstc-tcode, 'has no authorization check'.
ENDSELECT.
3Oct 12

Import user favorites into a role menu

Hi consultants,
did you ever wonder, what's behind the button "Import from file" in PFCG's Menu tab?

Well, it obviously allows you to upload a menu from a file, but expects a special file format: SAP Note 389675 has the details. You won't find this format anywhere in PFCG or elsewhere in your system, so it has to be created by you…

This usually makes the "Import from file" button hard to use and thus unpreferable!

The plan

Let's say, you're trying to revise (and minimize) the authorization in a SAP client ex post, i.e. when the system has been in use for some while and nobody took care of proper roles. Moreover some (key-) users might already have created their own favorites, which – hopefully – reflect their tasks in the system.

Wouldn't it be nice to be able to import those user favorites to a role and build adequate authorizations this way? Still there will be much to analyze and adjust — but it might be a good starting point!

Technical background

A user's favorites are stored in the table SMEN_BUFFC and SMEN_BUFFI (for the various kinds of link targets). So this is the place we'll get the menu data from.

The file format from the above mentioned SAP Note 389675 only supports a subset of all possible favorite types: folders, transaction codes, URLs, Knowledge Warehouse links and custom types (we won't deal with the last-mentioned one).
So in addition to reading and converting the favorites, we'll have to filter out all unsupported types of favorites.

Conversion report

Here's how to create the program that does the work:

  • Create a new report in SE38 and paste this source code (don't forget to set a program authorization group).
  • In the selection texts, tick "dictionary reference" for all parameters.
  • Activate & execute the program.

The selection screen allows you to select:

  • the user from whom to read the favorites and
  • an optional file to save the data to.

Once started, the report prints the converted favorites on screen and optionally saves it to the specified file.

Next steps

You might want to customize the report to download the favorites of several users at once — but be aware that you'll have to either save each user's favorites to its own file or deal with duplicate object IDs (and parent IDs and the sort order …)!

If you're interested in role menus, you might want to check the AGR_HIER* tables.

😀 Have fun!