,

TaiG Jailbreak werkt niet meer door iOS 8.4.1 update

Apple heeft sinds gisteren iOS 8.4.1 vrijgegeven en lost daarmee een aantal problemen op. De update zorgt er echter voor dat de TaiG jailbreak niet meer functioneert op deze nieuwe versie van iOS.

taig_icon

We hadden nog hoop dat de kwetsbaarheden niet gedicht waren, die TaiG gebruikte om ons toestel op iOS 8.4 te kunnen jailbreaken. Apple heeft echter in hun gedetailleerde omschrijving van de iOS 8.4.1 update laten weten dat de kwetsbaarheden gedicht zijn. Hierdoor is het niet mogelijk om iOS 8.4.1 te jailbreaken. Daarom raden wij je aan om niet te updaten naar iOS 8.4.1 als je geïnteresseerd bent in een jailbreak op je iPhone, iPad of iPod Touch.

Hieronder staat de gedetailleerde omschrijving van de kwetsbaarheden die gedicht zijn, die gebruikt werden door 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-IDCVE-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-IDCVE-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-IDCVE-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-IDCVE-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-IDCVE-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-IDCVE-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-IDCVE-2015-5774 : TaiG Jailbreak Team

Zoals je ziet benoemt Apple het TaiG team een aantal keer. Het gedetailleerde log bestand is hier te vinden.

 

Join the Forum discussion on this post

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *