Multiple Vulnerabilities in Apple Products Could Allow for Arbitrary Code Execution – PATCH NOW

OVERVIEW:
Multiple vulnerabilities have been discovered in Apple products, the most severe of which could allow for arbitrary code execution. Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. 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. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.
THREAT INTELLEGENCE:
Apple is aware of a report that CVE-2024-23296 was exploited in the wild.
SYSTEMS AFFECTED:
• Safari versions prior to 17.6
• iOS and iPadOS versions prior to 17.6
• iOS and iPadOS versions prior to 16.7.9
• macOS Sonoma versions prior to 14.6
• macOS Ventura versions prior to 13.6.8
• macOS Monterey versions prior to 12.7.6
• watchOS ersions prior to 10.6
• watchOS versions prior to tvOS 17.6
• visionOS versions prior to 1.3
RISK:
Government:
• Large and medium government entities: High
• Small government entities: Medium
Businesses:
• Large and medium business entities: High
• Small business entities: Medium
Home users: Low
TECHNICAL SUMMARY:
Multiple vulnerabilities have been discovered in Apple products, the most severe of which could allow for arbitrary code execution. Details of the vulnerabilities are as follows:
Tactic: Execution (TA0002):
Technique: Exploitation for Client Execution (T1203):
• An app with root privileges may be able to execute arbitrary code with kernel privileges. (CVE-2024-27878)
• An app may be able to overwrite arbitrary files. (CVE-2024-40827)
• A remote attacker may be able to cause arbitrary code execution. (CVE-2024-6387)
• An app may be able to execute arbitrary code with kernel privileges. (CVE-2024-27826)
Additional lower severity vulnerabilities include:
• Visiting a website that frames malicious content may lead to UI spoofing. (CVE-2024-40817)
• Processing maliciously crafted web content may lead to an unexpected process crash. (CVE-2024-40776, CVE-2024-40782, CVE-2024-40779, CVE-2024-40780, CVE-2024-40789, CVE-2024-40799)
• Processing maliciously crafted web content may lead to a cross site scripting attack. (CVE-2024-40785)
• Private Browsing tabs may be accessed without authentication. (CVE-2024-40794)
• An app may be able to bypass Privacy preferences. (CVE-2024-40774, CVE-2024-40814)
• Processing a maliciously crafted file may lead to unexpected app termination. (CVE-2024-40799, CVE-2024-40806, CVE-2024-40777, CVE-2024-40784, CVE-2024-27877)
• Processing a maliciously crafted video file may lead to unexpected app termination. (CVE-2024-27873)
• A malicious attacker with arbitrary read and write capability may be able to bypass Pointer Authentication. (CVE-2024-40815)
• An app may be able to read sensitive location information. (CVE-2024-40795)
• Processing an image may lead to a denial-of-service. (CVE-2023-6277, CVE-2023-52356)
• A local attacker may be able to determine kernel memory layout. (CVE-2024-27863)
• A local attacker may be able to cause unexpected system shutdown. (CVE-2024-40788)
• An app may be able to bypass Privacy preferences. (CVE-2024-40805, CVE-2024-40824)
• An attacker with physical access may be able to use Siri to access sensitive user data. (CVE-2024-40813)
• Photos in the Hidden Photos Album may be viewed without authentication. (CVE-2024-40778)
• An app may be able to access protected user data. (CVE-2024-27871, CVE-2024-40793, CVE-2024-27872)
• A shortcut may be able to use sensitive data with certain actions without prompting the user. (CVE-2024-40833, CVE-2024-40835, CVE-2024-40836, CVE-2024-40807)
• A shortcut may be able to bypass Internet permission requirements. (CVE-2024-40809, CVE-2024-40812, CVE-2024-40787)
• An attacker may be able to view sensitive user information. (CVE-2024-40786)
• An attacker with physical access may be able to use Siri to access sensitive user data. (CVE-2024-40818)
• An attacker with physical access to a device may be able to access contacts from the lock screen. (CVE-2024-40822)
• An attacker may be able to view restricted content from the lock screen. (CVE-2024-40829)
• Private browsing may leak some browsing history. (CVE-2024-40796)
• An app may be able to read Safari’s browsing history. (CVE-2024-40798)
• A malicious application may be able to access private information. (CVE-2024-40804)
• Multiple issues in Apache. (CVE-2023-38709, CVE-2024-24795, CVE-2024-27316)
• A malicious application may be able to bypass Privacy preferences. (CVE-2024-40783)
• An app may be able to leak sensitive user information. (CVE-2024-40775, CVE-2024-40823)
• Multiple issues in curl. (CVE-2024-2004, CVE-2024-2379, CVE-2024-2398, CVE-2024-2466)
• A malicious attacker with arbitrary read and write capability may be able to bypass Pointer Authentication. (CVE-2024-40815)
• A local attacker may be able to cause unexpected system shutdown. (CVE-2024-40816)
• An attacker may be able to cause unexpected app termination. (CVE-2024-40803)
• An app may be able to view a contact’s phone number in system logs. (CVE-2024-40832)
• A local attacker may be able to elevate their privileges. (CVE-2024-40781, CVE-2024-40782)
• An app may be able to modify protected parts of the file system. (CVE-2024-27882, CVE-2024-27883, CVE-2024-40800)
• An app may bypass Gatekeeper checks. (CVE-2023-27952)
• An app may be able to access information about a user’s contacts. (CVE-2024-27881)
• Third party app extensions may not receive the correct sandbox restrictions. (CVE-2024-40821)
• Enabling Lockdown Mode while setting up a Mac may cause FileVault to become unexpectedly disabled. (CVE-2024-27862)
• A shortcut may be able to bypass sensitive Shortcuts app settings. (CVE-2024-40834)
• A malicious app may be able to gain root privileges. (CVE-2024-40828)
• An app may be able to modify protected parts of the file system. (CVE-2024-40811)
• An attacker may be able to read information belonging to another user. (CVE-2024-23261)
• An attacker with arbitrary kernel read and write capability may be able to bypass kernel memory protections. Apple is aware of a report that this issue may have been exploited. (CVE-2024-23296)
• An app may be able to cause unexpected system termination. (CVE-2024-27804)
• An attacker in a privileged network position may be able to spoof network packets. (CVE-2024-27823)
Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. 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. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.
RECOMMENDATIONS:
We recommend the following actions be taken:
• Apply the stable channel update provided by Apple to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
o Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
o Safeguard 7.2 : Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
o Safeguard 7.6 : Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets: Perform automated vulnerability scans of externally-exposed enterprise assets using a SCAP-compliant vulnerability scanning tool. Perform scans on a monthly, or more frequent, basis.
o Safeguard 7.7 : Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
o Safeguard 16.13 Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
o Safeguard 18.1 : Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
o Safeguard 18.2 : Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
o Safeguard 18.3 : Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.

• Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
o Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
o Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.

• Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
o Safeguard 2.3: Address Unauthorized Software: Ensure that unauthorized software is either removed from use on enterprise assets or receives a documented exception. Review monthly, or more frequently.
o Safeguard 2.7: Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassessbi-annually, or more frequently.
o Safeguard 9.3: Maintain and Enforce Network-Based URL Filters: Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
o Safeguard 9.6: Block Unnecessary File Types: Block unnecessary file types attempting to enter the enterprise’s email gateway.

• Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
o Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.

• Block execution of code on a system through application control, and/or script blocking. (M1038: Execution Prevention)
o Safeguard 2.5 : Allowlist Authorized Software: Use technical controls, such as application allowlisting, to ensure that only authorized software can execute or be accessed. Reassess bi-annually, or more frequently.
o Safeguard 2.6 : Allowlist Authorized Libraries: Use technical controls to ensure that only authorized software libraries, such as specific .dll, .ocx, .so, etc., files, are allowed to load into a system process. Block unauthorized libraries from loading into a system process. Reassess bi-annually, or more frequently.
o Safeguard 2.7 : Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.

• Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (M1040: Behavior Prevention on Endpoint)
o Safeguard 13.2 : Deploy a Host-Based Intrusion Detection Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
o Safeguard 13.7 : Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.

REFERENCES:
Apple:
https://support.apple.com/en-us/HT201222
https://support.apple.com/kb/HT214121
https://support.apple.com/kb/HT214117
https://support.apple.com/kb/HT214116
https://support.apple.com/kb/HT214119
https://support.apple.com/kb/HT214120
https://support.apple.com/kb/HT214118
https://support.apple.com/kb/HT214124
https://support.apple.com/kb/HT214122
https://support.apple.com/kb/HT214123
CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-6277
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-27952
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38709
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52356
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-2004
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-2379
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-2398
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-2466
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-6387
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23261
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23296
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-24795
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27316
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27804
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27823
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27826
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27862
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27863
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27871
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27872
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27873
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27877
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27878
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27881
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27882
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27883
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40774
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40775
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40776
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40777
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40778
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40779
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40780
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40781
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40782
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40783
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40784
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40785
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40786
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40787
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40788
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40789
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40793
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40794
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40795
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40796
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40798
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40799
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40800
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40803
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40804
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40805
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40806
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40807
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40809
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40811
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40812
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40813
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40814
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40815
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40816
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40817
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40818
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40821
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40822
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40823
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40824
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40827
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40828
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40829
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40832
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40833
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40834
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40835
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40836