Adobe Patches 38 Flaws in Enterprise Software Products


After skipping last month, Adobe returned to its scheduled Patch Tuesday cadence with the release of fixes for at least 38 vulnerabilities in multiple enterprise-facing products.

After skipping last month, Adobe returned to its scheduled Patch Tuesday cadence with the release of fixes for at least 38 vulnerabilities in multiple enterprise-facing products.

The San Jose, California software maker said the flaws could expose users to code execution and privilege escalation attacks across all computer platforms.

The most serious vulnerabilities affect Adobe Experience Manager (AEM), the content management tool used by corporate marketing teams.  

Adobe said it patched at least 33 flaws in the AEM Cloud Service (Release 2022.10.0) and warned of the risk of serious hacker attacks.

”Successful exploitation of these vulnerabilities could result in arbitrary code execution and security feature bypass,” according to the company’s public documentation.

[ Read: VMware Patches VM Escape Flaw Exploited at Geekpwn Event ]

In a separate bulletin, Adobe said it fixed a privilege escalation issue in the Adobe Campaign Classic (ACC) product and urged Windows and Linux users to apply the available updates.

The company also pushed fixes for a quartet of memory leak issues in the Adobe Illustrator product. Adobe said the issues affect Illustrator 2022 on both Windows and macOS platforms.

The Adobe patches come on the same day virtualization technology giant VMware released urgent updates to fix security problems in multiple software products, including a virtual machine escape bug exploited at the GeekPwn 2022 hacking challenge.

The VM escape flaw, documented as CVE-2022-31705, was exploited by Ant Security researcher Yuhao Jiang on systems running fully patched VMware Fusion, ESXi and Workstation products.  

In a security bulletin issued Tuesday, VMWare slapped a CVSS severity rating of 9.3/10 and warned that a malicious actor with local administrative privileges on a virtual machine may exploit this issue to execute code as the virtual machine’s VMX process running on the host 


By Ryan Naraine on Tue, 13 Dec 2022 19:52:25 +0000
Original link