Menu Close

Apple Products Could Allow for Arbitrary Code Execution – PATCH NOW – TLP: CLEAR

.

TLP:CLEAR
MS-ISAC CYBERSECURITY ADVISORY

MS-ISAC ADVISORY NUMBER:
2024-009

DATE(S) ISSUED:
01/23/2024

SUBJECT:
Multiple Vulnerabilities in Apple Products Could Allow for Arbitrary Code Execution  

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 INTELLIGENCE:
Apple is aware of a report that CVE-2024-23222 may have been exploited. In addition, Apple is also aware of a report that CVE-2023-42916 and CVE-2023-42917 may have been exploited against versions of iOS before iOS 16.7.1.

SYSTEMS AFFECTED:

  • Versions prior to macOS Sonoma 14.3
  • Versions prior to macOS Ventura 13.6.4
  • Versions prior to macOS Monterey 12.7.3
  • Versions prior to watchOS 10.3
  • Versions prior to tvOS 17.3
  • Versions prior to iOS 15.8.1 and iPadOS 15.8.1
  • Versions prior to iOS 16.7.5 and iPadOS 16.7.5
  • Versions prior to iOS 17.3 and iPadOS 17.3
  • Versions prior to Safari 17.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):

  • Processing web content may lead to arbitrary code execution(CVE-2024-23213, CVE-2024-23209)
  • Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been exploited. (CVE-2024-23222)
  • An app may be able to execute arbitrary code with kernel privileges (CVE-2024-23212, CVE-2024-23208)
  • Processing maliciously crafted web content may lead to arbitrary code execution(CVE-2024-23214)
  • Processing web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been exploited against versions of iOS before iOS 16.7.1. (CVE-2023-42917)

Additional lower severity vulnerabilities include: 

  • A user’s private browsing activity may be visible in Settings (CVE-2024-23211)
  • A maliciously crafted webpage may be able to fingerprint the user (CVE-2024-23206)
  • An attacker may be able to decrypt legacy RSA PKCS#1 v1.5 ciphertexts without having the private key (CVE-2024-23218)
  • An app may be able to access sensitive user data (CVE-2024-23207, CVE-2024-23223, CVE-2024-23215, CVE-2023-42937, CVE-2024-23224)
  • Stolen Device Protection may be unexpectedly disabled (CVE-2024-23219)
  • A shortcut may be able to use sensitive data with certain actions without prompting the user (CVE-2024-23203, CVE-2024-23204)
  • An app may be able to bypass certain Privacy preferences (CVE-2024-23217)
  • An app may be able to view a user’s phone number in system logs (CVE-2024-23210)
  • Multiple issues in curl (CVE-2023-38545, CVE-2023-38039, CVE-2023-38546, CVE-2023-42915)
  • Processing a maliciously crafted image may result in disclosure of process memory (CVE-2023-42888)
  • Processing web content may disclose sensitive information. Apple is aware of a report that this issue may have been exploited against versions of iOS before iOS 16.7.1. (CVE-2023-42916)
  • An app may be able to bypass Privacy preferences (CVE-2023-40528)
  • A local attacker may be able to view the previous logged in user’s desktop from the fast user switching screen (CVE-2023-42935)
  • An app may be able to read arbitrary files (CVE-2023-42887)

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)
    • 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)
    1. 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.
    2. 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.
    3. 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)
    1. 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.
    2. 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/HT214055
https://support.apple.com/en-us/HT214056
https://support.apple.com/en-us/HT214057
https://support.apple.com/en-us/HT214058
https://support.apple.com/en-us/HT214059
https://support.apple.com/en-us/HT214060
https://support.apple.com/en-us/HT214061
https://support.apple.com/en-us/HT214062
https://support.apple.com/en-us/HT214063

CVE:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38039
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38546
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40528
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-42887
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-42888
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-42915
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-42916
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-42917
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-42935
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-42937
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23203
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23204
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23206
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23207
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23208
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23209
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23210
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23211
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23212
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23213
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23214
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23215
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23217
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23218
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23219
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23222
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23223
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-23224

Multi-State Information Sharing and Analysis Center (MS-ISAC)
Elections Infrastructure Information Sharing and Analysis Center (EI-ISAC)
31 Tech Valley Drive
East Greenbush, NY 12061

24×7 Security Operations Center
SOC@cisecurity.org – 1-866-787-4722

TLP:CLEAR
www.cisa.gov/tlp
Information may be distributed without restriction, subject to standard copyright rules.

Center for Internet Security

Northeast Headquarters | 31 Tech Valley Drive | East Greenbush, NY 12061 | Phone: 518-266-3460