Project

General

Profile

Wiki » History » Version 15

Linus, 12/25/2013 07:26 PM

1 5 Karsten
h2. SIMtester
2 2 Karsten
3 1 Karsten
The provided tools assess SIM card security in two dimensions:
4
5
* *Cryptanalytic attack surface.* Collect cryptographic signatures and encryptions of known plaintexts
6
7 9 Anonymous
* *Application attack surface.* Generate a list of all application identifiers (TAR) and find "unprotected" (MSL(Minimum Security Level)=0) applications
8 1 Karsten
9 5 Karsten
h3. Requirements
10 1 Karsten
11 6 Anonymous
* Java 1.7 (code can be easily tweaked to compile under Java 1.6 or even lower if needed)
12
* PC/SC reader (via pcsc daemon) –or–
13
* Osmocom phone (via libosmosim)
14 1 Karsten
15 5 Karsten
h3. Download
16 1 Karsten
17 15 Linus
# "Pre-compiled .jar":https://opensource.srlabs.de/attachments/download/81/SIMTester.tar.gz
18
# "Live-System":https://opensource.srlabs.de/projects/mobile-network-assessment-tools/wiki/GSMmap-live
19
# "Source code":https://opensource.srlabs.de:/git/SIMtester.git
20 1 Karsten
21 5 Karsten
h3. Instructions
22 1 Karsten
23 13 Linus
# Download "Tarball":https://opensource.srlabs.de/attachments/download/81/SIMTester.tar.gz –or– "Live-System":https://opensource.srlabs.de/projects/mobile-network-assessment-tools/wiki/GSMmap-live –or– "Source code":https://opensource.srlabs.de:/git/SIMtester.git
24 12 Linus
# unpack <pre> tar xvzf SIMtester.tar.gz</pre>
25 1 Karsten
26
h4. Running SIMTester on LiveISO
27
28 14 Linus
Choose "Run Test" -> "SIM" from main menu, follow instructions.
29
30 10 Anonymous
h4. Running SIMTester by hand
31
32
SIMTester is a Java application (JAR archive), both sources and binaries are accessible under SIMTester git (https://opensource.srlabs.de:/git/SIMtester.git).
33 12 Linus
34
Unpack: <pre> tar xvzf SIMtester.tar.gz</pre>
35 11 Anonymous
36
You can either compile your own JAR from sources or run the pre-compiled JAR in "binaries/" directory like this:
37
38
<pre>
39
java -jar SIMTester.jar <arguments>
40
</pre>
41
42 10 Anonymous
h5. General options
43
44
| command line option | description |
45
|*@-vp, --verify-pin <pin>@*|verifies the PIN, works for CHV1|
46
|*@-sp, --skip-pin@*|skips verification of a PIN and ignore permission errors (may produce incomplete results!)|
47
|*@-dp, --disable-pin <pin>@*|disables PIN, works for CHV1 (ideal for testing cards so no PIN database in needed)|
48
|*@-tf, --terminal-factory <PCSC/OsmocomBB>@*|what are you using as SIM card reader|
49
|*@-ri, --reader-index <index of a reader>@*|multiple PC/SC readers can be connected, first is 0|
50
51
h5. SIMTester contains 3 main functionalities:
52
53
h5. Fuzzer
54
55
Has its own intelligent logic, fuzzes ~120 chosen TARs, is divided into 3 modes:
56
* Full fuzzing (default) - all 15 keysets with all 16 fuzzing mechanisms
57
* Quick fuzzing (-qf option) - keysets 1 to 6, only 4 most successful fuzzing mechanisms
58
* Poke the card (-poke option) - same as quick fuzzing but only fuzzes 3 most common TARs (000000, B00001, B00010)
59
60
Custom keysets and TARs can be specified via *-t* and *-k* parameters (space being a delimiter between multiple values).
61
62
h5. TAR Scanner
63
64
Scans for valid TAR(Toolkit Application Reference) values by sending messages to them, has 2 modes:
65
* Full scan (-st option) - scans for all possible TAR values (0x000000 - 0xFFFFFF) - may take a few hours or several days depending on your SIM card speed
66
* Ranged scan (-str option) - scans for valid TAR values in pre-specified ranges to optimise the scanning duration
67
68
A starting value for Full scan can be specified using *-t* option.
69
A keyset used for sending messages can be specified using *-k* option (for both Full and Ranged scans).
70
71
Tip: run fuzzer first, see what keysets seem responsive (give answers other than none) and use one of those for TAR scanning, because if you use an inactive keyset it's very probable the card will NOT answer even on a valid TAR which makes TAR scanning non-functional.
72
73
h5. APDU Scanner
74
75
Scans for valid APDU(Application Protocol Data Unit) values (think of APDUs as of commands to the card) on TARs without any public APDU reference, it has 2 modes:
76
* LEVEL 1 scan (performed automatically after *Fuzzer* finishes and has found unprotected TARs with responses) - only scans for valid CLA(Class) 0x00 - 0xFF - it is performed via OTA(Over The Air) messages.
77
* LEVEL 2 scan (-sa option) - scans for both CLA(Class) 0x00 - 0xFF and INS(Instruction) 0x00 - 0xFF - it is performed locally on card I/O on initially selected application
78
79 7 Anonymous
h3. Dependencies
80
81
Software uses several libraries, if compiled from source the following libraries are needed:
82
83 8 Anonymous
* "Apache Common CLI 1.3":http://commons.apache.org/proper/commons-cli/
84
* "CombinatoricsLib 2.0":https://code.google.com/p/combinatoricslib/
85
* SIMLibrary - available in the git along with SIMTester
86 7 Anonymous
87 5 Karsten
h3. Mailing list
88 1 Karsten
89
A public mailing list for announcements and discussion can be found "here":https://lists.srlabs.de/cgi-bin/mailman/listinfo/simsec