Confirmed: iOS 8.4.1 patches the exploits used by the TaiG jailbreak

TaiG Exploits Fixed iOS 8.4.1

We were hopeful, but as suspected, Apple was just a little late in getting the security details about the iOS 8.4.1 release out to the public. As it turns out, iOS 8.4.1 does indeed patch the TaiG jailbreak, as rumored for the last month. Needless to say, you should stay away from iOS 8.4.1 if you’re at all interested in jailbreaking your iPhone or iPad.

Here are the security notes related to the exploits used by TaiG:

  • AppleFileConduitAvailable for: iPhone 4s and later, iPod touch (5th generation) and later, iPad 2 and laterImpact: A maliciously crafted afc command may allow access to protected parts of the filesystemDescription: An issue existed in the symbolic linking mechanism of afc. This issue was addressed by adding additional path checks.CVE-ID

    CVE-2015-5746 : evad3rs, TaiG Jailbreak Team

  • Air TrafficAvailable for: iPhone 4s and later, iPod touch (5th generation) and later, iPad 2 and laterImpact: AirTraffic may have allowed access to protected parts of the filesystemDescription: A path traversal issue existed in asset handling. This was addressed with improved validation.CVE-ID

    CVE-2015-5766 : TaiG Jailbreak Team

  • BackupAvailable for: iPhone 4s and later, iPod touch (5th generation) and later, iPad 2 and laterImpact: A malicious application may be able to create symlinks to protected regions of the diskDescription: An issue existed within the path validation logic for symlinks. This issue was addressed through improved path sanitization.CVE-ID

    CVE-2015-5752 : TaiG Jailbreak Team

  • Code SigningAvailable for: iPhone 4s and later, iPod touch (5th generation) and later, iPad 2 and laterImpact: A malicious application may be able to execute unsigned codeDescription: An issue existed that allowed unsigned code to be appended to signed code in a specially crafted executable file. This issue was addressed through improved code signature validation.CVE-ID

    CVE-2015-3806 : TaiG Jailbreak Team

  • Code SigningAvailable for: iPhone 4s and later, iPod touch (5th generation) and later, iPad 2 and laterImpact: A specially crafted executable file could allow unsigned, malicious code to executeDescription: An issue existed in the way multi-architecture executable files were evaluated that could have allowed unsigned code to be executed. This issue was addressed through improved validation of executable files.CVE-ID

    CVE-2015-3803 : TaiG Jailbreak Team

  • Code SigningAvailable for: iPhone 4s and later, iPod touch (5th generation) and later, iPad 2 and laterImpact: A local user may be able to execute unsigned codeDescription: A validation issue existed in the handling of Mach-O files. This was addressed by adding additional checks.CVE-ID

    CVE-2015-3802 : TaiG Jailbreak Team

    CVE-2015-3805 : TaiG Jailbreak Team

  • IOHIDFamilyAvailable for: iPhone 4s and later, iPod touch (5th generation) and later, iPad 2 and laterImpact: A local user may be able to execute arbitrary code with system privilegesDescription: A buffer overflow issue existed in IOHIDFamily. This issue was addressed through improved memory handling.CVE-ID

    CVE-2015-5774 : TaiG Jailbreak Team

As you can see, Apple credited TaiG numerous times in its security log and fixed tons of exploits. You can view the entire iOS 8.4.1 security log by clicking here.

What do you think about the demise of the TaiG jailbreak? Are you sad? How do you plan on handling it? Sound off in the comments below.