NeCoders shall not be held responsible for any cases of software/files being hacked due to the information provided in this article.
Welcome back to part 3 of the Building Security Awareness in .Net Assemblies series. In this article, I will share with you the possibility of breaking Strong Named .Net Assemblies. Make sure you have already read through part 1 and 2 before continuing on.
Questions pertaining to Strong Name
I do believe many others have the same doubts as I do on whether Strong Name keys could really protect the assembly from being tampered. I would like to share my doubts with you in this article.
- Question : Is Strong Name key secure?
- Answer : Yes, Strong Name key uses RSA 1024 bit encryption.
- Question : Is Strong Name key breakable?
- Answer : If you have enough computing power, time and knowledge on how to break RSA, the answer is yes.
- Question : Can Strong Name key be removed from .NET assemblies?
- Answer : Yes, it can be removed very easily if you know how.
The Demonstration Test machine specifications :
- Download the executable files that come with this article.
- Open your Visual Studio .Net 2003 command prompt.
- Make sure you are inside the CrackingIL/bin/debug directory.
- Type “ildasm CrackingIL.exe /out=CrackingIL.il”.
- You must be wondering, why we are repeating what we had done in part 1 and part 2 of the series. If you notice, the way to break Strong Name keys is by manipulating the Intermediate Language. But the problem is in part 2, we did modify the Intermediate Language and at the end when we tried to convert it back to an assembly, we will receive an error. I will explain in detail on which part of the Intermediate Language that you should modified to remove the Strong Name key.
- Open up the CrackingIL.il with a text editor. I use notepad.
- Take a look at the red boxes. From what I understand, each assemblies like System.Windows.Forms, System and mscorlib contains their own public key token and version number.
- Now, does our assembly contain a public key? The answer is yes. Before showing it to you, I will first show you 2 screenshots; one without Strong Name key and one with Strong Name key attached.
Without Strong Name :
With Strong Name :
- You will notice that the difference on both sides is that the Strong Name key assembly contains a public key. In order to tamper a Strong Named .Net Assembly, just remove that highlighted section. It will look like this.
- Now do some modifications to the existing Intermediate Language. You have to remove the registry checking so it will not prompt you for serial number or license. Look for this code.
- Then remove the lines of code from IL_0000 to IL_0075. You should have an output like this.
- Now just edit some text to prove that you have hijacked that Strong Named key .Net Assembly. Find the code with the phrase “Welcome to NeCoders” and replace it to “You are being hijacked, Strong Names are useless here”.
Change above to:
- Open your Visual Studio .Net 2003 command prompt, and type “ilasm CrackingIL.il”.
- Try to run CrackingIL.exe. You will see this.
- Congratulations! You had managed to manipulate .Net assemblies with Strong Name key attached to it.
Again, I hope you find this series of the article to be interesting. There will be more articles under this series, in terms of breaking and securing the .Net assemblies. Do check out article 4 when it is available as it will explaining the many theories in .NET security. This in return should provide you with a better understanding in this topic.