The GID key (Group ID key) is a 256-bit AES key shared by all devices with the same application processor. The GID key is part of how iOS encrypts software on the device (more explanation). This is one component of the iOS security system, which also includes SHSH signatures.
This key is different on each processor model (system on a chip) - in other words, the S5L8900 (chip for iPhone 3G for example) has a different key compared to the S5L8930 (A4 chip for iPhone 4, iPod touch (4th generation), etc.). On S5L8960 and later processors, the Secure Enclave has it's own GID that is separate from the AP's which is used to encrypt the SEP Firmware before delivery to the end user.
Apple explains GID keys in its official iOS security guide Archived 2015-03-11 at the Wayback Machine (page 9, chapter "Encryption and Data Protection"), along with UID keys:
"The device’s unique ID (UID) and a device group ID (GID) are AES 256-bit keys fused (UID) or compiled (GID) into the application processor during manufacturing. No software or firmware can read them directly; they can see only the results of encryption or decryption operations performed using them. The UID is unique to each device and is not recorded by Apple or any of its suppliers. The GID is common to all processors in a class of devices (for example, all devices using the Apple A8 processor), and is used as an additional level of protection when delivering system software during installation and restore. Integrating these keys into the silicon helps prevent them from being tampered with or bypassed, or accessed outside the AES engine. The UID and GID are also not available via JTAG or other debugging interfaces."
On S5L8900, the GID key was used to generate AES Key 0x837, used as the encryption key for IMG2 files. With the introduction of IMG3 in iOS 2.0, iOS started using KBAGs instead of the 0x837 key. iOS 7.0 introduced the IM4P File Format and IMG4 File Format for A7 and newer devices.
In iOS 3.0GM/3.0, a pseudo GID Key was used, which allowed getting firmware decryption keys for these firmwares without the device and with tools such as GitKeys or OpenSSL. See Decrypting Firmwares#S5L8900.
Potential attacks[edit source]
A hypothetical way to extract this key could be to perform some sort of side-channel attack (see also Talk:GID Key for more speculation about potential attacks).
A presentation from May/June 2011 that explains a variety of attacks aiming to get this kind of information out of a chip: Fault attacks on secure chips: from glitch to flash (Part 1) and Side-channel attacks: new directions and horizons (Part 2).
Research into AES key extraction using side-channel analysis, done from 2010 to 2012: developing new technology for efficient side-channel analysis - using a tool from Quo Vadis Labs Archived 2012-05-31 at the Wayback Machine.
CIA research into attacks[edit source]
According to this March 2015 article in The Intercept based on documents provided by Edward Snowden, the CIA has been particularly interested in figuring out how to extract GID keys as part of their efforts to get access to modifying iOS to insert spy software and to research further vulnerabilities:
"At the 2011 Jamboree conference, there were two separate presentations on hacking the GID key on Apple’s processors. One was focused on non-invasively obtaining it by studying the electromagnetic emissions of — and the amount of power used by — the iPhone’s processor while encryption is being performed. Careful analysis of that information could be used to extract the encryption key. Such a tactic is known as a "side channel" attack. The second focused on a "method to physically extract the GID key.'"(The first document Archived 2015-03-15 at the Wayback Machine and the second one.)
"According to the 2011 document describing the Jamboree presentations on Apple's processor, the researchers asserted that extracting the GID key could also allow them to look for other potential gateways into Apple devices. 'If successful, it would enable decryption and analysis of the boot firmware for vulnerabilities, and development of associated exploits across the entire A4-based product-line, which includes the iPhone 4, the iPod touch and the iPad.'"
The 2011 timing is interesting, since geohot had publicly released a powerful bootrom exploit (limera1n) for A4 devices in October 2010, which presumably the CIA was already using (probably one of the "very small number of security flaws, many of which are public, which Apple eventually patches" they mentioned). If a person has a bootrom exploit like limera1n, they can decrypt firmwares by generating the firmware keys from the KBAGs (since they can use the GID keys on-device even if they can't extract them) - see Firmware Keys. It's possible this talk had been written earlier and presented as still relevant for A5 and future chips.
Discussion of CIA research[edit source]
NerveGas wrote a blog post about the implications of that article. He says: "The UID key is what you’d want to get if you made an arrest and were looking to scrape data off of a suspect’s device. Instead, what CIA was trying to get instead was the GID, which is a key shared across an entire chip architecture (e.g. product line), that’s used for decrypting the low level boot firmware on a device...What that tells us is that CIA was NOT interested in getting forensic level access to personal data on a seized device in physical custody, but is instead more interested in cooking their own low level boot firmware to potentially deploy across an entire product line of device. With a private cache of exploits and/or cooked boot loader firmware, CIA could potentially infect millions of devices with malicious firmware to give them persistent access to monitor or surveil devices worldwide."
i0n1c wrote some tweets responding to the article and disputing what NerveGas said, including these (quoted in chronological order):
- "The GID key allows you to decrypt iDevice firmware files. It does not allow you to pretend to be Apple. For that you need to break RSA." (For context, RSA signatures are used in the SHSH system, which is Apple's digital signature system designed to make sure only official Apple software can be installed on iOS devices.)
- "The next thing is: I do not read in the abstracts linked by The Intercept that they actually succeeded in getting the GID key."
- "The abstract linked by The Intercept merely say that they are working on extracting the GID key and that it is work in progress."
- "Several Jailbreakers also tried hardware attacks to extract GID keys. Everybody with the capability did. So no surprise…"
- "The GID key does not enable you to prepare a fake firmware. For that you need first and foremost a digital signature."
- "The reason why the CIA and everybody else is after the GID key is simply because it allows decrypting firmware for reversing purposes."
- "BTW a single key for a single firmware file for a group is enough to create correctly encrypted (but not signed) firmware (no GID needed)"
- "With limera1n millions of people had access to the GID key via bootrom code. Not a single person managed to create a bad accepted firmware"
The overall Intercept article was somewhat controversial among security researchers, with comments in this Twitter thread and this post with responses, with disagreements about the goals of the CIA research and about which people should have been consulted as experts on the subject.
Related tools[edit source]
- IOCryptoAcceleratorFamily - "a collection of kernel extensions that provide hardware-accelerated cryptographic functions, e.g. SHA1, AES, pseudo-random number generator (PRNG), etc."
- crypto by planetbeing - "This package allows you to directly access the iPhone's AES engine from userland. You may encrypt and decrypt with the UID and GID keys, as well as any custom keys you provide."
- iphone-dataprotection - wiki includes a list of types of encryption keys used for data protection, including a chart of key hierarchy on iPhone 4.