Coddec released

July 14, 2008

Finally we’ve decided to release coddec to public. Well, it is not actual coddec we use “in-house” but a very first working version of it.

Source and binary are provided. Please don’t ask for documentation or how to use it, I think it is very straightforward. There is a little bug which fires exemptions in some cod files – it is easy to fix it so we’ve left it there for you :)

Coddec

Enjoy

dr bolsen


But battery ?

February 7, 2008

I’ve been thinking about the place where cryptographic keys module could be located and accidentally find  this  information .

The BlackBerry CS-2 Battery features a secure, cryptographic chip to ensure you’re using a battery specially designed to work with your BlackBerry device.

I am curious what kind of chip is that ? Can it be used for secure keys generation and storage for example ?


Application Registry

February 7, 2008

Application registry is a core RIM Java OS structure . To play with it add the following string

Object __appReg = Process.getAppRegistry();

to BB java project. We used “Hello World!” sample project from JDE. Sure you need correct the import section of your project by adding import net.rim.vm.*;.
Using JDE IDE set a breakpoint on the next line and execute your code in standard IDE emulator. When program stops at the breakpoint, check __appReg :)

By the way the public key mentioned in this post was discovered using this approach.


Blackberry Security Kernel – FIPS 140-2 Report

February 7, 2008

FIPS 140-2 Report .

Interesting brief description of the security keys and algorithms used in Blackberry.


8700c teardown analysis

February 7, 2008

All parts from Blackberry 8700c enumerated and documented here


What happened ?

February 7, 2008

Well to make a long story a little bit shorter – I am a dad again :). Basically that was the main reason for my silence since August last year.

Cheers


Bypass signature requirement for COD files

July 31, 2007

Actually it didn’t work as we had expected. We still cannot bypass signature control, but results, in fact, quite interesting.

After many unsuccessful experiments and reviews of both – SignatureTool and rapc , we decided to try another approach – net_rim_api. Our assumption was that any API call should be mapped to particular function prototype in net_rim_api library. If we can learn how it was done then the next step would be to create our own “prototypes” of system functions and try to bypass needs for application signing. Our assumption was “almost” correct. Why “almost” I’ll explain later.

What we did, we used information dumped from cod files, namely – class names and methods definitions, to create prototype java files. An example:

// ##########################################
// Decompiled by : coddec
// Module : XXXXXXXXXXXXXX.cod
// Module version : 4.2.1.89
// #########################################
package net.rim.vm;

public class Process
{

native public int getLastIdleCounter();
}

The trick is just simple to declare a function as native. Then the file was compiled using standard java compilator. The resulting class file was slightly corrected by JavaBite tool to remove constructor code, but I am not quite sure that it was strictly required. Anyway you are free to experiment.

Next step is to add our class file to ne_rim_api.jar file. This task is very-very simple. We used 7-Zip to accomplish that.

Well, that’s it. If in your project you call getLastIdleCounter(), rapc will compile your project without any signature warning. Why was it cool ? getLastIdleCounter() is just an example, using the same approach is possible to call system functions not using protected RIM API.

Unfortunately, it only worked on emulator. There was additional signature requirement we weren’t aware of. Signer ID for this one is 33 and it appears as “Secure API” in the error message. We couldn’t find any useful information regarding that, but it seems it is related to so called “Secure Device” flag and it works the same way as firewall rule – “Deny All”.

If it would be possible to turn the flag off … We are trying to figure out how …

By the way, the public key for Signer ID ( 33 ) is the same for all devices and BB emulator, it begins with 0x8F A7 61 CA 6E B6 94 5E 28 86 … the length is 128 bytes (1024 bits). It is physically located in rim*.sif file.

Another possibility would be replace this key with own public key, but it would be necessary to re-sign all system libraries using own private key as well. And we are not quite sure if it would be possible to patch sfi file at all as it might be signed too.


Follow

Get every new post delivered to your Inbox.