Multiple Vulnerabilities in Apple Products Could Allow for Arbitrary Code Execution

Description:

 Multiple vulnerabilities have been discovered in Apple Support for iOS, Safari, watchOS, tvOS, and iOS. The most severe of these vulnerabilities could allow for arbitrary code execution.

  • Apple Support for iOS is an application that provides assistance with your Apple device.
  • Safari is a web browser available for OS X.
  • watchOS is the mobile operating system for the Apple Watch and is based on the iOS operating system.
  • tvOS is an operating system for the fourth-generation Apple TV digital media player.
  • iOS is a mobile operating system for mobile devices, including the iPhone, iPad, and iPod touch.

Successful exploitation of the most severe of these vulnerabilities could result in arbitrary code execution within the context of the application, an attacker gaining the same privileges as the logged-on user, or the bypassing of security restrictions. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

Security Issues Fixed:

Multiple vulnerabilities have been discovered in Apple Support for iOS, Safari, watchOS, tvOS, and iOS. The most severe of these vulnerabilities could allow for arbitrary code execution. Details of these vulnerabilities are as follows:

  • A consistency issue existed in the handling of application snapshots. The issue was addressed with improved handling of message deletions, notes deletions, and application snapshots. (CVE-2018-4313, CVE-2018-4352)
  • A logic issue was addressed with improved restrictions. (CVE-2018-4325)
  • A logic issue was addressed with improved state management. (CVE-2018-4307)
  • A memory corruption issue was addressed with improved memory handling. (CVE-2018-4330)
  • Analytics data was sent using HTTP rather than HTTPS. This was addressed by sending analytics data using HTTPS. (CVE-2018-4397)
  • Multiple input validation issues were addressed with improved input validation. (CVE-2018-4305, CVE-2018-4363, CVE-2018-5383)
  • A permissions issue existed. This issue was addressed with improved permission validation. (CVE-2018-4356)
  • Clearing a history item may not clear visits with redirect chains. The issue was addressed with improved data deletion. (CVE-2018-4329)
  • Multiple inconsistent user interface issues were addressed with improved state management. (CVE-2018-4195, CVE-2018-4362)
  • Multiple validation issues were addressed with improved input sanitization. (CVE-2018-4335, CVE-2018-4338)
  • An attacker may be able to exploit weaknesses in the RC4 cryptographic algorithm. This issue was addressed by removing RC4. (CVE-2016-1777)
  • A local app may be able to read a persistent account identifier. This issue was addressed with improved entitlements. (CVE-2018-4322)

Successful exploitation of the most severe of these vulnerabilities could result in arbitrary code execution within the context of the application, an attacker gaining the same privileges as the logged-on user, or the bypassing of security restrictions. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

Affected Products and Solution:

  • Apple Support for iOS versions prior to 2.4
  • Safari versions prior to 12
  • watchOS versions prior to 5
  • tvOS versions prior to 12
  • iOS versions prior to 12

References:

Apple

https://support.apple.com/en-us/HT209106

https://support.apple.com/en-us/HT209107

https://support.apple.com/en-us/HT209108

https://support.apple.com/en-us/HT209109

https://support.apple.com/en-us/HT209117

CVE:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1777

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4195

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4305

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4307

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4313

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4322

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4325

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4329

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4330

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4335

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4338

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4352

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4356

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4362

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4363

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4397

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5383

Leave a Reply

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