Multiple Vulnerabilities in Adobe Products Could Allow for Arbitrary Code Execution

Multiple vulnerabilities have been discovered in Adobe products, the most severe of which could allow for arbitrary code execution.

• Animate is a multimedia authoring computer animation program.
• Bridge is a digital asset management application
• Illustrator is a vector graphics editor and design program.
• Adobe InCopy is a professional word processor.
• InDesign is an industry-leading layout and page design software for print and digital media.
• RoboHelp Server is a help authoring tool

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution. 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 in the wild.

Multiple vulnerabilities have been discovered in Adobe Products, the most severe of which could allow for arbitrary code execution. Details of these vulnerabilities are as follows
Tactic: Execution (TA0002):
Technique: Exploitation for Client Execution (T1203)
Technique: User Execution (T1204)

Adobe Animate

• Out-of-bounds Write, which could allow for arbitrary code execution. (CVE-2022-30664)

Adobe Bridge

• Out-of-bounds Write, which could allow for arbitrary code execution. (CVE-2022-28839, CVE-2022-28844, CVE-2022-28845, CVE-2022-28846, CVE-2022-28847)
• Out-of-bounds Write, which could allow for arbitrary file system write. (CVE-2022-28840)
• Improper Input Validation, which could allow for arbitrary code execution. (CVE-2022-28841, CVE-2022-28842, CVE-2022-28848)
• Use After Free, which could allow for arbitrary code execution. (CVE-2022-28842, CVE-2022-28849)
• Out-of-bounds Read, which could allow for a Memory Leak. (CVE-2022-28850)

Adobe Illustrator

• Out-of-bounds Write, which could allow for arbitrary code execution. (CVE-2022-30637, CVE-2022-30639, CVE-2022-30640, CVE-2022-30641, CVE-2022-30642, CVE-2022-30643, CVE-2022-30645, CVE-2022-30649)
• Improper Input Validation, which could allow for Arbitrary code execution. (CVE-2022-30638, CVE-2022-30646)
• Use After Free, which could allow for arbitrary code execution. (CVE-2022-30644, CVE-2022-30647, CVE-2022-30648)
• Out-of-bounds read, which could allow for a Memory leak. (CVE-2022-30666, CVE-2022-30667, CVE-2022-30668, CVE-2022-30669)

Adobe InCopy

• Heap-based Buffer Overflow which could allow for arbitrary code execution. (CVE-2022-30650, CVE-2022-30654)
• Out-of-bounds read, which could allow for arbitrary code execution. (CVE-2022-30651)
• Out-of-bounds Write, which could allow for arbitrary code execution. (CVE-2022-30652, CVE-2022-30653, CVE-2022-30656)
• Use After Free, which could allow for arbitrary code execution. (CVE-2022-30655, CVE-2022-30657)

Adobe InDesign

• Heap-based Buffer Overflow which could allow for arbitrary code execution. (CVE-2022-30658, CVE-2022-30661)
• Out-of-bounds Write, which could allow for arbitrary code execution. (CVE-2022-30659, CVE-2022-30662, CVE-2022-30663, CVE-2022-30665, CVE-2022-30660)

RoboHelp Server

• Improper Authroization which could allow for privelge escalation. (CVE-2022-30670)
  Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution. 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.

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution. 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 Adobe 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.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
• Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted sources. Inform and educate users regarding the threats posed by hypertext links contained in emails or attachments especially from un-trusted sources. (M1017: User Training)
  o Safeguard 14.1: Establish and Maintain a Security Awareness Program: Establish and maintain a security awareness program. The purpose of a security awareness program is to educate the enterprise’s workforce on how to interact with enterprise assets and data in a secure manner. Conduct training at hire and, at a minimum, annually. Review and update content annually, or when significant enterprise changes occur that could impact this Safeguard.
  o Safeguard 14.2: Train Workforce Members to Recognize Social Engineering Attacks: Train workforce members to recognize social engineering attacks, such as phishing, pre-texting, and tailgating.
• 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.
• 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.
  oSafeguard 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.
• Restrict execution of code to a virtual environment on or in transit to an endpoint system. (M1048 : Application Isolation and Sandboxing)
  o Safeguard 4.1 : Establish and Maintain a Secure Configuration Process: Establish and maintain a secure configuration process for enterprise assets (end-user devices, including portable and mobile, non-computing/IoT devices, and servers) and software (operating systems and applications). Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
• 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.