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.
SYSTEMS AFFECTED:
RISK:
Government:
Businesses:
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 most critical vulnerabilities are as follows:
Tactic: Initial Access (TA0001):
Technique: Drive-by Compromise (T1189):
· Processing maliciously crafted web content may lead to arbitrary code execution. (CVE-2022-42823, CVE-2022-32922, CVE-2022-32886, CVE-2022-32888, CVE-2022-32912)
· Processing maliciously crafted web content may disclose sensitive user information (CVE-2022-42824)
· Processing a maliciously crafted certificate may lead to arbitrary code execution (CVE-2022-42813)
· Processing a maliciously crafted image may lead to arbitrary code execution (CVE-2022-42795, CVE-2022-26730)
· Visiting a malicious website may lead to user interface spoofing (CVE-2022-42799)
· Processing a maliciously crafted file may lead to a denial-of-service or potentially disclose memory contents (CVE-2022-29458)
· Processing a maliciously crafted DMG file may lead to arbitrary code execution with system privileges (CVE-2022-32905)
· Processing a maliciously crafted gcx file may lead to unexpected app termination or arbitrary code execution (CVE-2022-42809)
Details of lower-severity vulnerabilities are as follows:
· An app may be able to execute arbitrary code with kernel privileges. (CVE-2022-32940, CVE-2022-32947, CVE-2022-42806, CVE-2022-32924, CVE-2022-42827, CVE-2022-32898, CVE-2022-32899, CVE-2022-32865, CVE-2022-32915, CVE-2022-32866, CVE-2022-32911, CVE-2022-32914, CVE-2022-42791)
· An app with root privileges may be able to execute arbitrary code with kernel privileges (CVE-2022-42829, CVE-2022-42830, CVE-2022-42831, CVE-2022-42832)
· An app may be able to access user-sensitive data (CVE-2022-42811, CVE-2022-42789, CVE-2022-32904, CVE-2022-42814, CVE-2022-42815)
· An app may be able to disclose kernel memory (CVE-2022-32936, CVE-2022-32864)
· An app may be able to modify protected parts of the file system (CVE-2022-32895, CVE-2022-32881)
· An app with root privileges may be able to access private information (CVE-2022-32862)
· An app may cause unexpected app termination or arbitrary code execution (CVE-2022-42820)
· An app may be able to modify protected parts of the file system (CVE-2022-42825)
· An app may be able to record audio using a pair of connected AirPods (CVE-2022-32946)
· A remote user may be able to cause kernel code execution (CVE-2022-42808, CVE-2022-32934)
· A shortcut may be able to check the existence of an arbitrary path on the file system (CVE-2022-32938)
· A remote user may be able to cause unexpected app termination or arbitrary code execution (CVE-2022-28739)
· An app may be able to leak sensitive kernel state (CVE-2022-32858)
· An app may be able to cause a denial-of-service (CVE-2022-32827)
· An app may be able to bypass Privacy preferences (CVE-2022-32902, CVE-2022-32918)
· A sandboxed process may be able to circumvent sandbox restrictions (CVE-2022-32890, CVE-2022-32892)
· An app may be able to gain elevated privileges (CVE-2022-42796)
· An app may be able to read sensitive location information (CVE-2022-42819, CVE-2022-32883, CVE-2022-32875)
· A user with physical access to an iOS device may be able to read past diagnostic logs (CVE-2022-32867)
· Multiple issues in curl (CVE-2022-32205, CVE-2022-32206, CVE-2022-32207, CVE-2022-32208)
· A user in a privileged network position may be able to intercept mail credentials (CVE-2022-32928)
· A malicious application may be able to read sensitive location information (CVE-2022-42788)
· A user may be able to cause unexpected app termination or arbitrary code execution (CVE-2022-3437, CVE-2021-39537)
· A sandboxed app may be able to determine which app is currently using the camera (CVE-2022-32913)
· Processing an image may lead to a denial-of-service (CVE-2022-1622)
· A user may be able to elevate privileges (CVE-2022-32908)
· A user in a privileged network position may be able to track user activity (CVE-2022-42818)
· A user with physical access to a device may be able to access contacts from the lock screen (CVE-2022-32879)
· An app may be able to bypass code signing checks (CVE-2022-42793)
· A user may be able to view restricted content from the lock screen (CVE-2022-42790)
· A user with physical access to a device may be able to use Siri to obtain some call history information (CVE-2022-32870)
· A remote user may be able to cause a denial-of-service (CVE-2021-36690)
· Multiple issues in Vim (CVE-2022-0261, CVE-2022-0318, CVE-2022-0319, CVE-2022-0351, CVE-2022-0359, CVE-2022-0361, CVE-2022-0368, CVE-2022-0392, CVE-2022-0554, CVE-2022-0572, CVE-2022-0629, CVE-2022-0685, CVE-2022-0696, CVE-2022-0714, CVE-2022-0729, CVE-2022-0943, CVE-2022-1381, CVE-2022-1420, CVE-2022-1725, CVE-2022-1616, CVE-2022-1619, CVE-2022-1620, CVE-2022-1621, CVE-2022-1629, CVE-2022-1674, CVE-2022-1733, CVE-2022-1735, CVE-2022-1769, CVE-2022-1927, CVE-2022-1942, CVE-2022-1968, CVE-2022-1851, CVE-2022-1897, CVE-2022-1898, CVE-2022-1720, CVE-2022-2000, CVE-2022-2042, CVE-2022-2124, CVE-2022-2125, CVE-2022-2126)
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:
1. Apply the stable channel update provided by Apple to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
2. 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)
3. Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
4. Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (Mitigation M1050 : Exploit Protection)
REFERENCES:
Apple:https://support.apple.com/en-us/HT213495
https://support.apple.com/en-us/HT213489
https://support.apple.com/en-us/HT213493
https://support.apple.com/en-us/HT213494
https://support.apple.com/en-us/HT213488
https://support.apple.com/en-us/HT213492
https://support.apple.com/en-us/HT213491
CVE: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36690
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39537
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0261
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0318
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0319
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0351
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0359
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0361
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0368
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0392
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0554
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0572
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0629
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0685
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0696
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0714
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0729
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0943
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1381
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1420
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1616
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1619
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1620
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1621
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1622
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1629
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1674
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1720
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1725
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1733
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1735
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1769
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1851
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1897
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1898
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1927
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1942
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1968
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2000
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2042
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2124
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2125
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2126
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3437
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26730
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28739
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29458
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32205
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32206
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32207
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32208
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32827
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32862
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32864
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32865
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32866
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32867
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32870
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32875
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32879
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32881
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32883
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32886
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32888
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32890
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32892
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32895
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32898
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32899
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32902
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32904
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32905
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32908
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32911
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32912
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32913
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32914
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32915
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32918
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32922
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32924
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32928
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32934
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32936
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32938
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32940
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32946
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32947
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42788
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42789
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42790
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42791
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42793
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42795
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42799
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42806
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42808
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42809
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42811
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42813
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42814
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42815
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42818
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42819
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42820
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42823
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42824
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42825
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42827
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42829
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42830
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42831
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42832