Multiple Vulnerabilities in Apple Products Could Allow for Arbitrary Code Execution

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.

There are currently no reports of these vulnerabilities being exploited.

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 attacker with physical access to a locked device may be able to view sensitive user information. (CVE-2024-44274)
• A malicious app may be able to run arbitrary shortcuts without user consent. (CVE-2024-44255)
• A malicious app may be able to access private information. (CVE-2024-44273)
• Processing a maliciously crafted font may result in the disclosure of process memory. (CVE-2024-44240, CVE-2024-44302)
• Parsing a file may lead to disclosure of user information. (CVE-2024-44282, CVE-2024-44279, CVE-2024-44281)
• Processing an image may result in disclosure of process memory. (CVE-2024-44215)
• Processing a maliciously crafted message may lead to a denial-of-service. (CVE-2024-44297)
• An app may be able to cause unexpected system termination or corrupt kernel memory. (CVE-2024-44285, CVE-2024-44277)
• A remote attacker may be able to break out of Web Content sandbox. (CVE-2024-40867)
• An app may be able to leak sensitive kernel state. (CVE-2024-44239)
• Restoring a maliciously crafted backup file may lead to modification of protected system files. (CVE-2024-44258, CVE-2024-44252)
• An attacker may be able to misuse a trust relationship to download malicious content. (CVE-2024-44259)
• Private browsing may leak some browsing history. (CVE-2024-44229)
• Processing a maliciously crafted file may lead to heap corruption. (CVE-2024-44218, CVE-2024-44126)
• An app may be able to access sensitive user data. (CVE-2024-44254, CVE-2024-44194, CVE-2024-44292, CVE-2024-44257, CVE-2024-44175)
• A malicious app may use shortcuts to access restricted files. (CVE-2024-44269)
• An attacker with physical access may be able to access contact photos from the lock screen. (CVE-2024-40851)
• An app may be able to access user-sensitive data. (CVE-2024-44263, CVE-2024-44216, CVE-2024-44211)
• A sandboxed app may be able to access sensitive user data in system logs. (CVE-2024-44278)
• An attacker may be able to view restricted content from the lock screen. (CVE-2024-44251, CVE-2024-44235, CVE-2024-44261)
• Processing maliciously crafted web content may prevent Content Security Policy from being enforced. (CVE-2024-44296)
• Processing maliciously crafted web content may lead to an unexpected process crash. (CVE-2024-44244)
• Maliciously crafted web content may violate iframe sandboxing policy. (CVE-2024-44155)
• Processing a maliciously crafted file may lead to unexpected app termination. (CVE-2024-44144, CVE-2024-44236, CVE-2024-44237)
• Multiple issues existed in Apache. (CVE-2024-39573, CVE-2024-38477, CVE-2024-38476)
• A sandboxed process may be able to circumvent sandbox restrictions. (CVE-2024-44270)
• An app may be able to modify protected parts of the file system. (CVE-2024-44280, CVE-2024-44295, CVE-2024-44253, CVE-2024-44196)
• A malicious app with root privileges may be able to modify the contents of system files. (CVE-2024-44260)
• An app may be able to access information about a user's contacts. (CVE-2024-44298)
• An attacker in a privileged network position may be able to leak sensitive user information. (CVE-2024-44213)
• An app may be able to read sensitive location information. (CVE-2024-44289, CVE-2024-44222)
• An attacker with physical access can input Game Controller events to apps running on a locked device. (CVE-2024-44265)
• A malicious application may be able to modify protected parts of the file system. (CVE-2024-44287, CVE-2024-44247, CVE-2024-44267, CVE-2024-44301, CVE-2024-44275)
• A malicious app may be able to cause a denial-of-service. (CVE-2024-44197)
• A person with physical access to a Mac may be able to bypass Login Window during a software update. (CVE-2024-44231)
• An attacker with physical access to a Mac may be able to view protected content from the Login Window. (CVE-2024-44223)
• An app may be able to break out of its sandbox. (CVE-2024-44256)
• A user may be able to view sensitive user information. (CVE-2024-44293, CVE-2024-44262)
• An app may be able to bypass Privacy preferences. (CVE-2024-44156, CVE-2024-44159)
• An attacker with root privileges may be able to delete protected system files. (CVE-2024-44294)
• An app may be able to access Contacts without user consent. (CVE-2024-40858)
• An app may be able to read arbitrary files. (CVE-2024-44195)
• Parsing a maliciously crafted file may lead to an unexpected app termination. (CVE-2024-44283, CVE-2024-44284)
• A malicious app may be able to create symlinks to protected regions of the disk. (CVE-2024-44264)
• A sandboxed app may be able to access sensitive user data. (CVE-2024-40855)
• An application may be able to break out of its sandbox. (CVE-2024-44122)
• An attacker with physical access may be able to share items from the lock screen. (CVE-2024-44137)

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.

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)
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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)
• 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.
• 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)
• 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.
• 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.
• 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.
• 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)
• 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)
• 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.
• 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.
• 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)
• 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.
• 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.