axi0mX releases Chronic Dev Team’s SHAtter exploit

The infamous SHAtter exploit has been shrouded in secrecy ever since its inception. Surprisingly, axi0mX has decided to make its source code public almost seven years after its release.

SHAtter exploit source code is now public

After seven years of its release, axi0mX has released SHAtter’s source code to the public.

For those who don’t know, the chief architect of the SHAtter vulnerability was Joshua Hill aka p0sixninja. Other hackers such as Musclenerd and pod2g were also involved in the project.

axi0mX wasn’t even doing iOS hacking and development back in the day so it’s unsure how the hacker accessed the source code.

jailbreak

Although there’s another copy of it floating around on the internet, it’s not as detailed as the one provided by axi0mX.

If you are interested in this exploit, you can check its source out on the hacker’s Github repository.

It will give you great insight into the inner workings of the iOS operating system and how hackers develop exploits and jailbreak tools.

What is SHAtter?

Veteran jailbreakers clearly remember this exploit and the aura of mystery surrounding the exploit.

However, novice users who only recently joined the jailbreak scene don’t know any names other than Pangu or yalu102.

SHAtter exploits a vulnerability present in the A4 processor. It utilizes a special USB control message to fool the BootROM.

This leads to a full compromise of the entire bootchain, which allows hackers to inject arbitrary code into iOS.

hacker

This exploit is compatible only with Apple devices with the A4 SoC, namely –

  • iPad
  • iPhone 4
  • iPod touch 4
  • Apple TV 2

Unfortunately, SHAtter never saw the light of the day. The primary reason behind this was the release of limera1n jailbreak by George Hotz.

Despite its age, this bug is still useful for legacy development. Hackers can potentially develop an untethered jailbreak tool using this exploit.

For more jailbreak news and updates, follow and like us on Facebook and Twitter.

Leave a Reply