Breaking the Windows Script Encoder
The Windows Script Encoder (SCRENC.EXE) is a Microsoft tool that can be used to encode your scripts (i.e., JavaScript, ASP pages, VBScript).
Yes... encode, not encrypt.
The use of this tool is to be able to prevent people from looking at, or modifying, your scripts. Microsoft recommends using the Script Encoder to obfuscate your ASP pages, so in case your server is compromised the hacker would be unable to find out how your ASP applications work.
You can download the Windows Script Encoder v1.0 at: www.microsoft.com/downloads/details.aspx?FamilyID=e7877f67-c447-4873-b1b0-21f0626a6329&displaylang=en
The documentation already says the following:
"Note that this encoding only prevents casual viewing of your code; it will not prevent the determined hacker from seeing what you've done and how."
(By the way, because of this text, I did not deem it necessary to inform Microsoft of this article).
Also, an encoded script is protected against tampering and modifications:
"After encoding, if you change even one character in the encoded text, the integrity of the entire script is lost and it can no longer be used."
So we can make the following observations:
- We are a "determined hacker." *grins*
- If it's about "preventing casual viewing," what's wrong with encoding mechanisms like a simple XOR or even uuencoding, Base64, and URL-encoding?
- Anyone using this tool will be convinced that it's safe to hard-code all usernames, passwords, and "secret" algorithms into their ASP-pages. And any "determined hacker" will be able to get to them anyway.
Okay. So even Microsoft says this can be broken. Can't be difficult then. It wasn't. Writing this article took me at least twice the time I needed for breaking it. But I think this can be a very nice exercise for anyone who wants to learn more about analyzing codes like this, with known plaintext, known ciphertext, and unknown key and algorithm.
(Actually, a COM object that can do the encoding is shipped with IE 5.0, so reverse engineering this will reveal the algorithm, but that's no fun, is it?)
So, How Does This Work?
The Script Encoder works in a very simple way. It takes two parameters: the filename of the file containing the script, and the name of the output file, containing the encoded script.
What part of the file will be encoded depends on the filename extension, as well as on the presence of a so-called "encoding marker." This encoding marker allows you to exclude part of your script from being encoded. This can be very handy for JavaScript, because the encoded scripts will only work on Microsoft IE 5.0 or higher.... (of course this is not an issue for ASP and VBScripts that run on a web server!).
Say, you've got this HTML page with a script you want to hide from prying eyes:
This is what it looks like after running Windows Script Encoder:
As you can see, the <SCRIPT LANGUAGE="..."> has been changed into JScript.Encode.
The Script Encoder uses the Scripting.Encoder COM object to do the actual encoding. The decoding will be done by the script interpreter itself (so we cannot simply call a Scripting.Decoder, because that doesn't exist).
Okay, Let's Play!
Cute.
As you can see, @#@& appears to be a newline (@# = Carriage Return, @& = Line Feed), and the position of a character does (sometimes...) matter. (The first time HaiHai becomes CCbCmk and the second time it's CmrCmk).
Let's just encode a line with a lot of A:
The Algorithm
After staring at this for some time, I discovered that the RED part was repeating (actually, the entire string is repeating itself after 64 characters).
Also, it seems to be that the character A has three different representations: b, z, and )
If you encode a string of B you'll see the same pattern, but with different characters.
This means the encoding will look something like this:
I assumed that only the ASCII codes 32 to 126 inclusive, and 9 (Tab) are encoded. The rest is being escaped in a similar fashion as CR and LF.
What's left is the stuff before and after the encoded string. I did not look into this (yet). It will probably contain a checksum and some information about the length of the encoded script.
The Encoding Tables
So now we'll have to find out those tables for the encoding. The pick_encoding table is very simple to discover by just looking at the pattern that was the result of encoding all those A:
The string of A had a CR and LF in front of them, so after skipping the first two digits, you'll see that 0, 1, 2, 0, 2, 0, 0, 2 perfectly matches b, ), z, b, z, b, b, z, having b = 0, ) = 1, and z = 2.
The other table is a matrix that holds three different representations for each character. Which one will be used, depends on the pick_encoding table. To find out this matrix, just make a file that will cause every character to be encoded three times. Make sure the algorithm is "reset" by padding the lines so each group will start on a 64-byte boundary:
Etcetera. Note that there is only 59 bytes of padding a because the CR and LF at the end of the line are counting too! (59 + 2 + 3 = 64).
After encoding this, you can remove the encoded a again, as well as the @#@& for the CR and LF. This is what remains:
d7i P~, "Ze JEr a:[ ^yf ]Yu ['L BvE `cv #b* eMC _Q3 ~SB OR R c z&J !TZ Fq8 +y &f2 c*W *Xl v+ G{F %0R ,1O )l= iIp @!@!@! 'x{ @*@*@* g_Q @$@$@$ b)z A$~ Z/; f9G 23A sow M!V Cu_ q(& 9Bx |Fn SJd H\t 1Hg r6} nKh p}5 I]" ?j U KP: ji` .#j q (po 5eI }t\ $,] -w' TDY 7?% {m| =|# lCm 48( m^1 N[9 +n 0W6 oLT t44 krb L%N 3V0 Vs^ :hs xU WGK w2a ;5$ D .M /dk YOD E;! \-7 hAS 6aX XzH y". `P uk- 8N) U=?So what is this?
It's the encoded representation of the ASCII characters 9, and 32 through 126. Every character has got three different representations, so this sums up to 3 * (127 - 32 + 1) = 288 characters.
You'll see that the <, >, and @ characters are escaped too, resulting in the following table:
I've removed the @!, @*, and @$ from the encoded text too and replaced them with question marks, so the table will stay nice. This is what you get as a hex dump:
So, encoding character c at position i goes as follows:
- Look up which representation to use (the first, second or third): pick_encoding[i mod 64]
- Find the representations in the huge table: encoding[c * 3]
- Encoded character = encoding[c * 3 + pick_encoding[i % 64]];
Because the table starts at 9 and then goes to 32, you'll have to do some corrections. But we'll get to that later, as we are not really interested in encoding after all. We want to be able to do some decoding!
The Decoding Tables
The pick_encoding table will stay the same. This is because each character (except for the escaped ones, of course) will be in the same place as the original. Then, we could just look up the encoded character in the table. For instance, an A in encoded text (hex 0x41), occurs on these places in the "encoding" table:
- Row 9, group 4, representation 1 = F
- Row 10, group 3, representation 3 = I
- Row 23, group 1, representation 2 = {
So an A in the encoded text is an F, I, or {, depending on it's position.
Where there is a 0 in the pick_encoding table, it's an F.
For 1 it's an I.
For 2 it's a {.
You don't want to go looking through the encoding table each time, trying to find those numbers. By transforming the encoding table into another table, you can just go to position 0x41 (actually, 0x41 - 31 to correct it skipping everything below space except for Tab), and pick the correct representation:
With this matrix, it's very simple to look up the original character by simply looking it up in our table.
Assume i is the position of the character and c is the character again. Then: decoded = transformed[pick_encoding[i % 64]][c];
The Encoding of the Length-Field
So what's left is to find out how many characters there are to decode.
If we just keep decoding stuff, we will decode part of the HTML that's behind the encoded script. This can be avoided by stopping when a < is encountered (< will never appear in an encoded stream), but even in the case we are looking at a "pure" script file (*.js or *.vbs), there is some checksum stuff behind the actual data, which we should not decode.
I created a number of files of different size. By giving them a *.js extension the entire file is encoded without the Script Encoder looking for a start marker.
The results are below (only the first 12-bytes are displayed):
The length seems to be encoded in the 5th to 10th byte, and 41 appears to be representing zero.
The first byte of the length seems to be increasing with one when the length increases with 4. Also, the second byte alternates between 41, 51, 67, and 77.
If you look at length 166, this value is 0x70, where it should be: 0x41 + (166 / 4) = 0x6A
So something goes wrong, and it can be narrowed down to length 104, where it suddenly jumps from 0x5A to 0x61.
This puzzled me for a long time, until I realized that: 0x5A = Z and 0x61 = a
And yes, the length turns out to be Base64 encoded indeed. :)
The Checksum
At the end of the encoded data is apparently some kind of checksum. I did not look into this any further.
The decoder programThe further working of the decoder program, which can be downloaded from the scrdec home page, is left as an exercise to the reader.
It's implemented as a "Turing-like" state machine. The decoder will treat .js and .vbs files as fully encoded, while .htm(l) and .asp files are seen as files that contain script amongst other things - like HTML code.
The decoder simply takes two arguments: input filename (encoded), and output filename (decoded).
There is one thing lacking in the decoder: the value of the <SCRIPT LANGUAGE="..."> attribute, is not changed back into the original form. You'd better use a tool like sed for that.
Conclusion
It's not just sad that Microsoft made a tool like this. They've probably asked Bill Gates' little nephew to write this code. The really bad part is that Microsoft actually recommends people to use this piece of crap, and because of that, people will rely on it, even though the documentation hints that it's unsafe. (Nobody reads the docs anyway...)
Security by obscurity is a bad, bad idea. Instead of encouraging that approach, Microsoft should educate programmers to find other ways to store their passwords and sensitive data, and tell them that an algorithm or any other piece of code that needs to be "hidden," is just bad design.
Code: scrdec18.c
Code: scrdec18.exe Windows Script Decoder v1.8 (52k EXE) (Manual)
Usage
Script Decoder is a simple Win32 command line executable that is used as follows:scrdec <infile> <outfile> [<code page>]There's no fancy stuff like wildcard support or overwriting the input file with the output file. If you really want to do that, just use the DOS for command:md decoded for %a in (*.asp) do scrdec %a decoded\%a del *.asp move decoded\*.asp . rd decodedNote that the FOR command does not support long file names.
Make backups for safety!
After running the decoder, you'll see that all garbled blocks of script, like<%#@~^swIAAA==@#@&@!Z OJz@#@&zJ;/WaX.kTtO©~8,,R~HbmDKdG0DP;W.wG.mYrW PzVs~"ko4OkP]+knM\n9R@#@&0!x1OkKx~DrWHZWM.+1YAMGADv#`@#@&~,kW`%>will have been decoded into their original form. Please note that you will still have to manually strip the '.Encode' out of the 'JScript.Encode' and 'VBScript.Encode' in the <script language=".."> tags!
The script decoder recognises all encoded blocks that start with the sequence #@~^, so it will correctly decode 'plain files' that only contain script, ASP style blocks <%script%>, and <script language="...">script<script> blocks.
Starting with version 1.2, the script decoder has the ability to use different code pages so it can decode scripts that contain Asian characters. If you want to decode such scripts, just supply the code page identifier as the third parameter.Id / Code Page 932 / Japanese 936 / Chinese (Simplified) 950 / Chinese (Traditional) 949 / Korean (Wansung) 1361 / Korean (Johab)If you want to decode scripts using another code page, then you do not need to specify it.
Alternatively, you can use this little VBScript that Gene Naftulyev sent me (thanks dude!), or the further improved version by Ninio Erez.